|Parsing C typedefs using yacc firstname.lastname@example.org (Andrew Dunbar) (1995-12-09)|
|Re: Parsing C typedefs using yacc email@example.com (1995-12-10)|
|Re: Parsing C typedefs using yacc firstname.lastname@example.org (1995-12-17)|
|From:||email@example.com (Ken Walter)|
|Date:||10 Dec 1995 15:20:19 -0500|
|Keywords:||C, parse, comment|
Andrew Dunbar <firstname.lastname@example.org> writes:
:>I'm trying to parse C using yacc but I've hit a problem with
That is one of the BIG problems with C/C++ declarations. They can look
like expressions unless you have feedback from previous declarations.
Nothing much you can do about it except accept the ambiguity.
[At least one parser I've seen that didn't actually keep a symbol
table has used the ugly but fairly effective hack of presuming that
mystery tokens that start with a capital letter are typedef
Return to the
Search the comp.compilers archives again.