Using of parse tree externally

[Dupont, Michael]

Dear all,

There are two areas that I have been looking into in the last months,
I am not finished and I did not want to raise false hopes, but I think some
of it might be of use :

one is the tree structure, which I have built a C++ Wrapper for and can
output it to a simple HTML/XML file.
After that I realised that you need to understand the grammar to understand
the nodes for a good part.

Then I was working on some modules to read the dump file produced with -Dy
when compiling.
Although only for the c-parse.y grammer, I have a set of perl modules that
will graph out
syntax trees and show *how* it is used and not just the what is possible.

I have made a interface for both to the VCG toolkit for displaying the
graphs.

Denis, The work is not done yet and still needs to be cleaned up, but maybe
it would be of interest to you?

Ideally we could output a parse tree *WITH* the Tree Nodes attached in a
rich XML file and post process them with XLST.

What do you think?

Mike
-----Original Message-----
From: Mark Mitchell [ mailto:mark@codesourcery.com ]
Sent: 09 October 2000 16:36
To: dyp@perchine.com
Cc: gcc@gcc.gnu.org
Subject: Re: Using of parse tree externally


>>>>> "Denis" == Denis Perchine <dyp@perchine.com> writes:

    Denis> I work on static analisys tool. And would like to use parse
    Denis> tree produced by C++ gcc frontend. The question is did
    Denis> someone did some movements to store parse tree in a file
    Denis> and read it back in a program which is outside gcc tree?
    >>  Nobody has done this, yes.  This is something we have talked
    >> about extensively, and have some ideas about, but has not been
    >> done.

    Denis> Could you please point me to the discusson, if it is not so
    Denis> hard for you.

The discussion I am familiar with is internal to CodeSourcery; there
is no mail archive or URL to provide.

Thanks,

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com
-- 
This communication contains information which is confidential and 
may also be privileged.  It is for the exclusive use of the 
intended recipient(s).  If you are not the intended recipient(s), 
please note that any distribution, copying or use of this 
communication or the information in it is strictly prohibited.  
If you have received this communication in error, please notify 
the sender immediately and then destroy any copies of it.