Re: Need extraction tool(parser)

"David W. Coppit" <dwc3q@mamba.cs.virginia.edu>
13 Jul 1997 11:42:27 -0400

          From comp.compilers

Related articles
Need extraction tool(parser) rsimmons@xmission.xmission.com (Roger Simmons) (1997-06-30)
Re: Need extraction tool(parser) stevef7@erols.com (The Flanagans) (1997-07-08)
Re: Need extraction tool(parser) mzraly@athena.mit.edu (1997-07-09)
Re: Need extraction tool(parser) dwc3q@mamba.cs.virginia.edu (David W. Coppit) (1997-07-13)
Re: Need extraction tool(parser) nandu@lucent.com (1997-07-21)
| List of all articles for this month |

From: "David W. Coppit" <dwc3q@mamba.cs.virginia.edu>
Newsgroups: comp.compilers
Date: 13 Jul 1997 11:42:27 -0400
Organization: University of Virginia
Keywords: parse, tools, available, C++

Check out Sage++. It will parse the code and then provide an OO interface
to the AST.


Michael S. Zraly wrote:


> Actually the parsing could be fairly simple-minded, given you really
> only need to identify {}-delimited code bodies, handle comments and
> literals, and whatnot. Just be careful with method bodies in class
> declarations: you probably don't want the whole class declaration
> printed out.


This would work, depending on how accurate you would want your tool to be.
The following would be pretty hard to capture:


void foo() {
    cout << "This is a brace: {\n"; // This prints out a brace ("{")
    cout << "{Can't parse quotes easily! (\")}\n";
}


David


_________________________________________________________________________
David Coppit - Graduate Student coppit@cs.virginia.edu
The University of Virginia http://www.cs.virginia.edu/~dwc3q
--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.