Eric Blake wrote: > there is too much risk that a user > will use those characters in his local encoding, but not the > byte sequence that M4 recognizes based on a different > encoding of those characters. Indeed. I thought this problem could be solved by having every file declare its quote characters at the beginning (and reset then to [ ] at the end), but this doesn't work: when a macro is defined in a.m4 and invoked from b.m4, the quotes in effect for b.m4 will be used for parsing the inner definition of the macro - while the quotes for a.m4 apply to the outermost quotes. Oh well :-( > Although I agree that using non-ASCII quotes would eliminate ambiguity, > it would make debugging tougher, when the character appears correctly > in the editor but is in the wrong encoding. Indeed. Bruno _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
