RE: [cdt-core-dev] Parser comments

[Sebastien Marineau <sebastien@xxxxxxx>]

Hi John,
 
> Sebastien wrote: 
> > - declarations of the kind:
> > 
> > int kdecl foobar(int a) {
> > }
> > 
> > where kdecl is defined in a header as some compiler-specific 
> > attribute.
> > "kdecl" 
> > confuses the parser. One thought (we'd discussed this before) 
> > is to have a
> > list
> > of ignored keywords that the user can set up (these could 
> > include some of
> > the gcc
> > extensions).
> 
> The strategy that we've taken (since we do not have the build 
> model yet) is
> to have better error-handling on undefined symbols like this. 
>  I've added in
> some extra error-handling code this morning that makes that 
> example work in
> the Outline view, I will submit a patch today for it.  For 
> the full-parse
> scenario (i.e. for indexing) we fully intend to make the 
> choice of parser
> and predefined symbols driven by build configuration.  

I'm not sure that in that case the build model will be enough, unless
the build model also supplies detailed information above keyword
extensions to the C language. You may still want an "ignore" list
that is tied directly to the parser.

> 
> > Also, I updated the ui.tests plugin, but got compile errors 
> > in the DomTests
> > and ParserSymbolTableTests files. Checked in a fix.
> 
> I don't see any checkins from you when I check resource history.  What
> exactly was the problem?  Are we using the wrong version of junit or
> something? 

Sorry, I had mailed the patch but not checked in the code yet. It should
be now. I'm using the 2.0.2 platform, and those files were not compiling
to to lacking constructors. Should be in CVS now.

Thanks,

Sebastien

> 
> JohnC 
> _______________________________________________
> cdt-core-dev mailing list
> cdt-core-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-core-dev
>