| Related articles |
|---|
| `javadoc` for c++ Marcus.Rohrmoser@lrz-muenchen.de (Marcus Rohrmoser) (1998-10-13) |
| Re: `javadoc` for c++ wender@par.univie.ac.at (1998-10-17) |
| Re: `javadoc` for c++ jerry@swsl.co.uk (1998-10-17) |
| Re: `javadoc` for c++ qjackson@wave.home.com (Quinn Tyler Jackson) (1998-10-17) |
| Re: `javadoc` for c++ dwight@pentasoft.com (1998-10-17) |
| Re: `javadoc` for c++ Marko.Makela@HUT.FI (Marko =?ISO-8859-1?Q?M=E4kel=E4?=) (1998-10-17) |
| Re: `javadoc` for c++ objsoft@netcom.com (1998-10-17) |
| Re: `javadoc` for c++ comments@cygnus-software.com (Bruce Dawson) (1998-10-17) |
| Re: `javadoc` for c++ leichter@smarts.com (Jerry Leichter) (1998-10-17) |
| [2 later articles] |
| From: | jerry@swsl.co.uk (Jerry Evans) |
| Newsgroups: | comp.compilers |
| Date: | 17 Oct 1998 01:41:28 -0400 |
| Organization: | Frontier Internet Services Limited |
| References: | 98-10-079 |
| Keywords: | C++, tools |
I'd like to know the same. The PCCTS grammar included with CCCC
(http://www.fste.ac.cowan.edu.au/~tlittlef) might be a good place to
start. This parses C++ well enough to generate McCabe (and other)
metrics. I'm trying to find the time to investigate further.
Jerry.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.