This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: config-lang.in fragments
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: Nathanael Nerode <neroden at twcny dot rr dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: 26 Jun 2003 06:15:56 -0300
- Subject: Re: config-lang.in fragments
- Organization: GCC Team, Red Hat
- References: <20030620042849.GA1494@doctormoo>
On Jun 20, 2003, Nathanael Nerode <neroden@twcny.rr.com> wrote:
> #2 looks like the way to go, but it demands some cleanup of the variable
> usage in config-lang.in fragments so that they never clobber anything
> at either level.
I think it's the other way round. config-lang.in implicitly defines
an interface, that front-ends that are not part of the GCC tree have
come to rely on. Changing the variable names in config-lang.in and
expecting such different names in the top-level will gratuitously
break such front-ends. The right approach would be to make sure names
defined in config-lang.in do not conflict with code in the top level.
Should conflicts arise, rename variables in the top level, but don't
change the interface unless you really have to.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer