On Thu, 14 Dec 2006, Hans Aberg wrote: > Another idea that came to my mind, which I just mention, is to separate Bison > language and compiler options. Language options should then go in the .y file, > and the compiler options in some other file. But perhaps this is not the > practise of other compilers. > > But by this idea, language options should then not be alterable by startup > arguments. In particular, %language should only not be duplicated by a > --language. Perhaps this idea is what you sense intuitively.
I'm afraid I don't know what is considered a "language option" versus a "compiler option". Also, separate input files sounds like a paradigm shift (and a lot of implementation work) that I don't think we're ready for.
