config-lang.in fragments

[Nathanael Nerode <neroden at twcny dot rr dot com>]

The way the config-lang.in fragments are processed by top level 
configure (and to some extent gcc/configure) is grotesque.

I've been trying to figure out a better way to do it.  (For the top 
level bootstrap project, I should look at "$boot_language" at the top
level, but I really don't want to code that in the same style as the
existing stuff, cause ICK ICK ICK.)

I've come up with a small number of options.
1. Use a different, more easily parseable format.
2. Use them the way they were meant to be, by including them directly
with . ${config-lang.in} statements.
3. Like #2, but have separate fragments for the top level and the gcc 
level configure scripts.

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

Would patches to do this be acceptable?  Or is there a preferred 
alternative?

-- 
Nathanael Nerode  <neroden at gcc.gnu.org>
Don't use the GNU FDL for free documentation.  See
<http://home.twcny.rr.com/nerode/neroden/fdl.html>