Related articles |
---|
Looking for C declaration parser lehotsky@max.tiac.net (1995-02-06) |
Re: Looking for C declaration parser agesen@Xenon.Stanford.EDU (1995-02-06) |
Re: Looking for C declaration parser flisakow@cae.wisc.edu (1995-02-06) |
Re: Looking for C declaration parser vinall@VNET.IBM.COM (1995-02-07) |
Re: Looking for C declaration parser rankin@eql.caltech.edu (1995-02-07) |
Re: Looking for C declaration parser kik@ironwood.cray.com (1995-02-08) |
Re: Looking for C declaration parser probertm@ariz.library.ucsb.edu (1995-02-11) |
Re: Looking for C declaration parser jejones@microware.com (1995-02-13) |
Newsgroups: | comp.compilers |
From: | flisakow@cae.wisc.edu (Shawn Flisakowski) |
Keywords: | C, tools |
Organization: | College of Engineering, University of Wisconsin-Madison |
References: | 95-02-067 |
Date: | Mon, 6 Feb 1995 23:17:15 GMT |
Alan Lehotsky <lehotsky@max.tiac.net> 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.
Shaun
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.