On Aug 30, 2012, at 6:05 AM, Axel Naumann <[email protected]> wrote:
> Hi,
>
> To implement (performant) string based lookup functionality we'd like to
> call some Parser functions that are currently inaccessible. Attached
> patch is one solution; we'd place the calls through a class deriving
> from Parser. Making some key parsing functions (the ones we use :-)
> public is another option.
>
> Rationale: the public Parser interfaces do string -> AST node
> operations; we do not want to create AST nodes nor do we even have valid
> C++ code, think lookup("int") where "int" is not a valid C++ declaration
> that the public Parser interfaces expect.
I'm fine with the general notion of opening up the parser more, but what
specific functions are you looking for? Those two 'private' access specifiers
cover a ton of functionality, much of which should stay internal to the parser.
- Doug
_______________________________________________
cfe-commits mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
