RE: [cdt-dev] new API for error parsers
thanks for starting the wiki-page!
It is important that we make a difference between breaking and
API changes. The breaking changes must be read and understood by
that needs to port existing work from CDT 5.x to CDT 6.0.
It is good to know about non-breaking changes also, but it is safe to
--> I divided the page into two sections, accordingly. We could also
separate pages, if you prefer.
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Elena Laskavaia
> Sent: Thursday, October 23, 2008 6:32 PM
> To: CDT General developers list.
> Subject: Re: [cdt-dev] new API for error parsers
> Importance: Low
> Committed, I updated API page:
> Elena Laskavaia wrote:
> > I am trying to fix
> > about trimming problem for error parsers.
> > It has been open for ages. I don't think we can simply fix
> it we need
> > a new API.
> > I suggest we create new interface IErrorParser2 which has a
> > function(s) that tells what lines we want.
> > Current possible options:
> > - as is now
> > - untrimmed string <=1000 chars
> > - untrimmed string <=1000 chars with ending \n and \r
> (Doubt that it
> > is needed though)
> > - string as is (including >1000 chars)
> > - whole buffer (without cutting by \n)
> > See proposed interface code here:
> > https://bugs.eclipse.org/bugs/attachment.cgi?id=115836
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> cdt-dev mailing list