Related articles |
---|
C Compiler in C++ stanarevic@hotmail.com (2002-05-08) |
Re: C Compiler in C++ loewis@informatik.hu-berlin.de (2002-05-12) |
Re: C Compiler in C++ dnovillo@redhat.com (Diego Novillo) (2002-05-12) |
Re: C Compiler in C++ journeyman@compilerguru.com (2002-05-12) |
Re: C Compiler in C++ thp@cs.ucr.edu (2002-05-12) |
Re: C Compiler in C++ rbates@southwind.net (Rodney M. Bates) (2002-05-13) |
Re: C Compiler in C++ lex@cc.gatech.edu (Lex Spoon) (2002-05-13) |
Re: C Compiler in C++ alexc@world.std.com (2002-05-17) |
[5 later articles] |
From: | loewis@informatik.hu-berlin.de (Martin v. =?iso-8859-1?q?L=F6wis?=) |
Newsgroups: | comp.compilers |
Date: | 12 May 2002 00:02:22 -0400 |
Organization: | Humboldt University Berlin, Department of Computer Science |
References: | 02-05-039 |
Keywords: | C, symbols |
Posted-Date: | 12 May 2002 00:02:22 EDT |
stanarevic@hotmail.com (Nemanja Stanarevic) writes:
> Does anyone know of a good way (or generally accepted way) of
> representing the parse tree for C declarations using a similar class
> hierarchy?
I think your approach is quite reasonable, and I know that atleast gcc
takes the same approach - you first have to collect declspec,
declarator, etc, and only then can find out what kind of declaration
you got.
Regards,
Martin
Return to the
comp.compilers page.
Search the
comp.compilers archives again.