Le 28 janv. 2012 à 14:06, Akim Demaille a écrit :
>> void
>> quote_init (void)
>> {
>> if (getenv ("BISON_C_QUOTING_STYLE"))
>> bison_quoting_style = shell_quoting_style;
>> set_quoting_style (0, QA_ELIDE_OUTER_QUOTES);
>> }
>
> - locale_quoting_style does not seem to obey to
> QA_ELIDE_OUTER_QUOTES. Is this on purpose?Well, it's actually the result of the fact that I have used set_quoting_style instead of set_quoting_flags. I am now understanding that we can't use just one rule for them all. For instance in -input.y:5.12-13: $$ for the midrule at $2 of 'exp' has no declared type -input.y:5.24-25: $2 of 'exp' has no declared type +input.y:5.12-13: $$ for the midrule at $2 of exp has no declared type +input.y:5.24-25: $2 of exp has no declared type if for instance we have a symbol name "rule" for instance, the messages will be obfuscated. Likewise in messages like -glr-regr18.y:26.18-24: result type clash on merge function 'merge': <type2> != <type1> +glr-regr18.y:26.18-24: result type clash on merge function merge: <type2> != <type1> it is really clear that it's the name of the function in the first case, much less in the second. I will prepare something less systematic.
testsuite.log
Description: Binary data
