This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Using of parse tree externally
- To: gcc at gcc dot gnu dot org
- Subject: Re: Using of parse tree externally
- From: Marc Espie <espie at quatramaran dot ens dot fr>
- Date: Thu, 19 Oct 2000 09:57:35 +0200
- Organization: Ecole Normale Superieure (quatramaran)
- References: <200010121919.MAA01165@penguin.transmeta.com>
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. :-)
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.
3/ nobody has thought of another way to do that.
4/ somebody has thought a ludicrously complicated and long and absurd process
to do it, that requires gnu-make, and gnu-m4, and libtool, and gnu-ADA to
do things, and then got his senses back and thought `Nah, even the FSF
wouldn't fall for it'.
Seriously, nothing exists still.