[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cdt-dev] Ready for M3 yet?
|
An ideal solution would be to continue to support both 3.3 and 3.2 for
as long as possible/practical. Lets put little more effort into this
before giving up on 3.2.
-sergey
On 11/6/06, Doug Schaefer <DSchaefer@xxxxxxx
> wrote:
That's true. Good point.
I'm using Eclipse 3.3 to make sure
it continues to meet the needs of CDT 4.0 since that is what it'll
support in the end (as John just mentioned). I am currently using my patched
CDT with M3 so I can continue working that way.
There's no doubting this has put us
all in a tough spot.
I'm currently using CDT
4.0 together with Eclipse 3.2 for my everyday C++ work, which is a great way to
find bugs, or see where new features are needed. My working environment
includes bunch of other plugins compatible with 3.2. If switching to 3.3 breaks
any of the plugins I depend upon, I will have to give up on using CDT 4.0 for
my everyday work.
-sergey
On 11/6/06, Sergey
Prigogin <eclipse.sprigogin@xxxxxxxxx>
wrote:
Would be nice to wait
until 3.3 becomes more mature. Breaking compatibility with 3.2 before it
happens can be painful.
-sergey
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev