Akim Demaille <[EMAIL PROTECTED]> writes: > Why not keeping a colon? > > syntax error: unexpected %s > syntax error: unexpected %s, expecting %s > syntax error: unexpected %s, expecting %s or %s > syntax error: unexpected %s, expecting %s or %s or %s > syntax error: unexpected %s, expecting %s or %s or %s or %s
I thought it better to use the traditional message formats, unless there's a good reason to change. If I recall correctly, GCC uses the exact same wording in its own parsers (which are now hand-built for C and C++, sigh) so translators can share the translations. While we're on the subject, if Bison ever changes the wording of a translatable message that goes into a generated parser, we'll need to keep the old wording in the message translation table, so that older programs will still be localized properly. This is because the message translation tables for Bison-generated parsers are not versioned. This was a conscious design decision at the time: Bruno Haible and I figured that message spellings wouldn't get changed very often.
