| RE: [cdt-dev] CDT 5.0 Plan posted |
|
Thanks, we’ll definitely take a look at
any patches you can contribute. Talking to Andrew F and Markus last week, even
they are having a hard time at it and they’ve been in this code for the last
year J. We need to find some way to clone Andrew N and bring him back. Or
my intern from last winter…
From: Sergey Prigogin
[mailto:sprigogin@xxxxxxxxxx] I'm ready to contribute.
I've already started looking into 201174,
but, as you said, this code takes quite a bit of time to get used to. On 10/1/07, The CDT is a contribution driven open source project.
Unfortunately, we lost our expertise in the template support code in the DOM a
couple of years ago. Andrew F and Markus are trying to rebuild that expertise,
but without additional contributions, these bugs may not get fixed. The refactoring work is being done by different people and is
really a separate issue. You could say that we shouldn't do content assist
until the CDT learns how to understand all the code, but I'm not sure everyone
would agree with that.
From: Sergey Prigogin [mailto:eclipse.sprigogin@xxxxxxxxx]
In 5.0, or even in 4.0.x, I'd like to see a concerted
effort toward eradicating remaining holes in C++ template support. See 175470,
201174,
201177,
201204.
Template support deficiencies severely limit usefulness of all CDT features
that depend on index accuracy. Serious work on C++ refactoring doesn't make
sense until CDT learns how to understand all code, not just part of it. On 10/1/07,
Hey
gang, I
have posted the plan I captured at the summit for CDT 5 to the Planning section
of the wiki. Please feel free to edit. Note that these are just proposals until
bugs are created with the CDT 5.0 target milestone set, at which point they
become commitments.
http://wiki.eclipse.org/CDT/planning/5.0
BTW,
I've also created the 5.0 milestone so that you can do that J . I've also
created the 4.0.3 milestone (end of Feb 08) to go along with the 4.0.2 (end of
Nov 07). Cheers,
|