Re: [cdt-core-dev] Open C++ Parser

["Alain Magloire" <alain@xxxxxxx>]

> 
> This message is in MIME format. Since your mail reader does not understand
> this format, some or all of this message may not be legible.
> 
> ------_=_NextPart_001_01C2A211.E09B67E0
> Content-Type: text/plain
> 
> Thanks Alain, we definitely want to line up on strategy and work together to
> make the right choices.
> 

We are very open on this, the more merrier 8-).

> Right now the focus is on performance since we're hoping to replace ctags
> and gather cross-reference information for the index.  We will likely need
> to have races to see which parser is faster.  I still don't have a sense of
> this yet.
> 

When working on this, some of the issues(very briefly):

- Macro definition our tied to th builder.
  #define _OLD_COMPAT_
  #include <stdio.h>

  parsing stdio.h depending on the defines will not show the same symbols.

- external includes
- defining a stategy for the storing mechanism, the indexer
  could play a major role in holding the information.
- limiting the scope/depth of the parsing.  Not every one needs
  the AST(to drill down to the blocks).

etc ...

> The second issue will be extensibility.  We're running into that quickly as
> the two compilers we're using here for testing (g++ and VC++) both extend
> C++ in wacky ways.  The parser strategy will need to handle this.  I'm not
> sure if JavaCC handles subclassing (I know ANTLR does) so this may be easier
> to do with a handwritten parser.
> 
> I'll let everyone know when we've reached a reasonable level of quality and
> we can start comparing the options in more detail.
> 

Thanks.