Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] API change for 179393

I have no problem with this. I'm not convinced we need an API freeze at this
stage of CDT's life. Maybe if we had more plug-ins building on top of us
that might be important. But I'm not sure everyone feels this way.

Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, http://cdtdoug.blogspot.com


> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Chris Recoskie
> Sent: Tuesday, April 03, 2007 2:19 PM
> To: cdt-dev@xxxxxxxxxxx
> Subject: [cdt-dev] API change for 179393
> 
> 
> Folks,
> 
> While I was on vacation Mike posted a patch to Bugzilla for the following
> bug:
> 
> 179393:  factor IScanner.addDefinition(IMacro) into its own interface
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=179393
> 
> This patch requires extracting part of the IScanner interface into another
> interface.  This allows other non-IScanner based parsers such as our C99
> parser to be able to pull macro definitions from the index.
> 
> Since this requires some small API changes I would like to get consensus
> on
> applying this patch before I do so.  Are there any objections before I go
> ahead and do this?  No one has commented on the bug.
> 
> ===========================
> 
> Chris Recoskie
> Team Lead, IBM CDT Team
> IBM Toronto
> http://www.eclipse.org/cdt
> 
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev


Back to the top