Using of parse tree externally

[Dupont, Michael]

Hi Marc, Gaby.

I am still thinking about how I am going to publish my work properly.

The work that I have done so far is :

1. Implement a C++ Interface to the Tree object.
2. Dump the Output of the Tree Nodes to XML-Like HTML
3. Write a Perl Parser for those nodes and put them into a Graph Object.
4. Output the Graph for VCG tool to visualize them.

I have published an older version but it is not ready for intergration,
it seems that even some people have looked at my code but I have gotten
feedback yet.

It is a very difficult to dig through the tree nodes because of the
complexity of the tree structure and the amount of the
data involved. 

I have not gotten any hate mails 


-----Original Message-----
From: Gabriel Dos Reis [ mailto:gdr@codesourcery.com ]
Sent: 19 October 2000 12:18
To: Marc Espie
Cc: gcc@gcc.gnu.org
Subject: Re: Using of parse tree externally


Marc Espie <espie@quatramaran.ens.fr> writes:

| In article < 200010122001.NAA09483@racerx.synopsys.com > you write:
| >
| >Exactly.  It's best to avoid this whole fight by finding some way of
| >implementing the desired functionality (e.g. static analysis tools) in a
| >less risky way.
| 
| It looks to me like this debate has been going on for years.
| So far, no-one has come forward and found a less risky way to implement
| the desired functionality.
| 
| There might be a few reasons for that (some of them highly inflamatory):
| 1/ no-one really knows how to tweak the code anyway, and saying it's not
| a good idea for political reasons let us save face. :-)

The job is technically doable.  But working on GCC is not just technical.
Which brings us to the next (political) reason:

| 2/ people have started on the work, but gotten so much political hate-mail
| (`you're going to KILL THE GPL. I hate your guts.') that they stopped.

Or people have started the work but refrain from publishing their in
fear of getting such mails -- which in effect is equivalent to having
nothing. 

It is an ironical situation that a reading of "free software
philosophy" prevents free software.  

-- Gaby
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.