* doc/standards.texi: Modify examples to show the new usage pattern
for program_name.
1) The fact that this is ensconced in the coding standards makes me
worry more than ever about compatibility. For one thing, why define the
same symbol program_name as a new, incompatible, type? Can't we name
the function `get_program_name' or something? Then at least working
code will not just bomb out.
This seems a rather fundamental thing to be changing. Aren't we
breaking tons of existing programs? This seems like a bad thing.
Saying "well, you shouldn't get new stuff from gnulib unless you want to
recode your program" doesn't seem like a very good argument to me.
Is it so impossible to do something that is backwards-compatible?
2) Nevertheless, if this is perceived as the way to go, I will ask rms
about it. He has to approve any change to the coding standards.
(And I am skeptical he will approve this.)
Thanks,
karl
_______________________________________________
bug-gnulib mailing list
bug-gnulib@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnulib
