Future/bison
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/bison.git synced 2026-03-09 12:23:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

* NEWS: Bison-generated C parsers now use the _ macro to

Browse Source 
translate strings.
* data/yacc.c (_) [!defined _]: New macro.
All English strings wrapped inside this macro.
* doc/bison.texinfo (Bison Parser): Document _.
* po/POTFILES.in: Include src/parse-gram.c, since it now
includes translateable strings that parse-gram.y doesn't.
This commit is contained in:
Paul Eggert
2005-04-14 00:08:56 +00:00
parent a749a69501
commit 1ce590705a
5 changed files with 55 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
doc/bison.texinfo
View File

@@ -1166,7 +1166,14 @@ start with a function called @code{main}; you have to provide this, and
arrange for it to call @code{yyparse} or the parser will never run.
@xref{Interface, ,Parser C-Language Interface}.
Aside from the token type names and the symbols in the actions you
If your code defines a C preprocessor macro @code{_} (a single
underscore), Bison assumes that it can be used to translate
English-language strings to the user's preferred language using a
function-like syntax, e.g., @code{_("syntax error")}. Otherwise,
Bison defines a no-op macro by that name that merely returns its
argument, so strings are not translated.
Aside from @code{_} and the token type names and the symbols in the actions you
write, all symbols defined in the Bison parser file itself
begin with @samp{yy} or @samp{YY}. This includes interface functions
such as the lexical analyzer function @code{yylex}, the error reporting