[cdt-dev] Eclipse M6 versus the CDT

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[cdt-dev] Eclipse M6 versus the CDT

From: Douglas Schaefer <dschaefe@xxxxxxxxxx>
Date: Wed, 30 Mar 2005 21:22:47 -0500
Delivered-to: cdt-dev@xxxxxxxxxxx
List-archive: <http://eclipse.org/pipermail/cdt-dev>
List-help: <mailto:cdt-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=unsubscribe>

It's not pretty folks. If you haven't tried it out yet, there are a number 
of API changes that affect the CDT. The biggest is in the MemoryBlock 
stuff in the debugger but there are others. We may need to break away from 
M5 at some time before declaring M6 if we can't make the changes in a 
backwards compatible way. Meanwhile, back to M5a...

Doug Schaefer
Ottawa Lab, IBM Rational Software Division

Prev by Date: Re: [cdt-dev] Automatic configure/build of CVS C/C++ repositories?
Next by Date: Re: [cdt-dev] Missing source/output exclusion filter options in CDT
Previous by thread: [cdt-dev] RE: Debug API Proposals
Next by thread: [cdt-dev] Multi version Tool-chain support enhancement request..
Index(es):
- Date
- Thread

Breadcrumbs