Related articles |
---|
[3 earlier articles] |
Re: C parser danwang74@gmail.com (Daniel C. Wang) (2004-08-04) |
Re: C parser tmk@netvision.net.il (2004-08-05) |
C parser skyanhf@yahoo.com.cn (=?gb2312?q?sky=20yan?=) (2004-08-05) |
Re: C parser codeworker@free.fr (2004-08-10) |
Re: C parser sid@igor.ics.uci.edu (Siddharth Choudhuri) (2004-08-11) |
C parser temple@deakin.edu.au (DAVID) (1997-07-16) |
Re: C parser drh@microsoft.com (Dave Hanson) (1997-07-18) |
Re: C parser cort@shay.ecn.purdue.edu (1997-07-22) |
From: | "Dave Hanson" <drh@microsoft.com> |
Newsgroups: | comp.compilers |
Date: | 18 Jul 1997 12:32:58 -0400 |
Organization: | Microsoft Corp. |
References: | 97-07-086 |
Keywords: | C, tools |
DAVID <temple@deakin.edu.au> wrote...
> I need a tool which will parse a 'C' file and extract the following
> a list of all functions return type of those functions number and
> type of parameters to those functions
>
> [If you can't find anything off the shelf, the protoize program which
> converts prototyped to unprototyped C and back should be a good place to
> start. It lives with the GNU stuff. -John]
it's very easy to build an lcc "backend" to this--we've built such browers
very quickly by editing the "symbolic" backend that comes with lcc.
if i get a chance, i'll post one of these to the lcc contributed software area
(ftp://ftp.cs.princeton.edu/pub/packages/lcc/contrib/).
dave hanson
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.