Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| Reusing free parsers for modern C++ briansmith@iname.com (Brian Smith) (2000-05-08) |
| Re: Reusing free parsers for modern C++ bruce+usenet@cenderis.demon.co.uk (Bruce Stephens) (2000-05-10) |
| Re: Reusing free parsers for modern C++ broonie@tardis.ed.ac.uk (Mark Brown) (2000-05-12) |
| Re: Reusing free parsers for modern C++ bogawa@vovida.com (2000-05-15) |
| Re: Reusing free parsers for modern C++ rsherry@home.com (Robert Sherry) (2000-05-22) |
| Re: Reusing free parsers for modern C++ idbaxter@semdesigns.com (Ira D. Baxter) (2000-05-24) |
| From: | bogawa@vovida.com (Bryan Ogawa) |
| Newsgroups: | comp.compilers |
| Date: | 15 May 2000 23:47:32 -0400 |
| Organization: | Posted via Supernews, http://www.supernews.com |
| References: | 00-05-034 |
| Keywords: | C++, parse |
On 8 May 2000 00:45:37 -0400, Brian Smith <briansmith@iname.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 <bogawa@vovida.com> http://www.vovida.com/
Return to the
comp.compilers page.
Search the
comp.compilers archives again.