Then again, with a fixed naming scheme, users can simply drop, say,
"glr.c#" in the bison lib dir and bison will automagically use it
without having to know it exists (is that desirable?).
Not sure, for example in Java a sensible output filename would not have
any ".tab", so some knowledge of the language needs to be there in Bison
to make such choices.
Also, "glr.c#" is not really a nice filename, it should be "glr.cs" and
the language directive arguments would be "C#" (possibly with a synonym
"C-Sharp").
And bison could
postprocess the default filenames based on the platform it's on (e.g.
change "lalr1.c++" to "lalr1.cxx" for DJGPP).
Agreed. Or just use the extension which ".y" maps to, which would be
hopefully platform-independent -- ".cc" in the case of C++.
Paolo
