[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: i18n for yacc backend messages

From: Hans Aberg
Subject: Re: i18n for yacc backend messages
Date: Sun, 17 Apr 2005 14:10:00 +0200

At 01:17 -0700 2005/04/17, Paul Eggert wrote:
+* When generating verbose diagnostics, Bison-generated C parsers no longer
+  quote the literal strings associated with tokens.  For example, for
+  a syntax error associated with '%token NUM "number"' they might
+  print 'syntax error, unexpected number' instead of 'syntax error,
+  unexpected "number"'.

My guess is that the change causes in general %token <name> "<string>", the <string> to be interpreted as a C-encoded string, and outputs the way C outputs them. This is the simplest way, and also what I suggested. Perhaps the comment above should have an addition, clarifying that, as well.
  Hans Aberg

reply via email to

[Prev in Thread] Current Thread [Next in Thread]