|Reusing free parsers for modern C++ firstname.lastname@example.org (Brian Smith) (2000-05-08)|
|Re: Reusing free parsers for modern C++ email@example.com (Bruce Stephens) (2000-05-10)|
|Re: Reusing free parsers for modern C++ firstname.lastname@example.org (Mark Brown) (2000-05-12)|
|Re: Reusing free parsers for modern C++ email@example.com (2000-05-15)|
|Re: Reusing free parsers for modern C++ firstname.lastname@example.org (Robert Sherry) (2000-05-22)|
|Re: Reusing free parsers for modern C++ email@example.com (Ira D. Baxter) (2000-05-24)|
|From:||firstname.lastname@example.org (Bryan Ogawa)|
|Date:||15 May 2000 23:47:32 -0400|
|Organization:||Posted via Supernews, http://www.supernews.com|
On 8 May 2000 00:45:37 -0400, Brian Smith <email@example.com> wrote:
>I am looking for comments and suggestions from people that have used
>the C++ front end of GCC or any other C++ parser for source code
>analysis. I'd like to hear about the documentation and learning curve
>I only need the front end to give me enough information to do the following:
>* generate a file dependency graph
Depending on what you need, GCC is probably capable of doing this now
via the -M flag, which generates make-compatible file dependencies.
This works fine for C++ as well as C.
Bryan K. Ogawa <firstname.lastname@example.org> http://www.vovida.com/
Return to the
Search the comp.compilers archives again.