|Looking for C declaration parser email@example.com (1995-02-06)|
|Re: Looking for C declaration parser agesen@Xenon.Stanford.EDU (1995-02-06)|
|Re: Looking for C declaration parser firstname.lastname@example.org (1995-02-06)|
|Re: Looking for C declaration parser vinall@VNET.IBM.COM (1995-02-07)|
|Re: Looking for C declaration parser email@example.com (1995-02-07)|
|Re: Looking for C declaration parser firstname.lastname@example.org (1995-02-08)|
|Re: Looking for C declaration parser email@example.com (1995-02-11)|
|Re: Looking for C declaration parser firstname.lastname@example.org (1995-02-13)|
|From:||email@example.com (Shawn Flisakowski)|
|Organization:||College of Engineering, University of Wisconsin-Madison|
|Date:||Mon, 6 Feb 1995 23:17:15 GMT|
Alan Lehotsky <firstname.lastname@example.org> wrote:
>I'm looking for a tool that parses C declarations and constructs a
>simple symbol table. I want to use this to parse simple .h files and
>generate equivalent data structures in other languages, such as PL/I.
>I suppose I could start with a complete C front-end, but that would be
>a lot of work to reduce to just a declaration parser.
I am working a C interpreter. I am not very far yet, but I have
a flex/bison lexer/parser that parse Ansi C code (or nearly)
and preprocessor statements. This would save your program the
trouble of passing files through cpp first.
My program has a symbol table a few other things, but not much else,
so you would probably have to "build-up" a ways to get what you're
looking for, but IMHO, that is much easier than trying to rip
sections out of complicated code.
Send mail for info or a copy of what I have so far.
Return to the
Search the comp.compilers archives again.