Le 6 mars 08 à 03:20, Joel E. Denny a écrit :
This patch, not yet committed, adds the above and fixes a few other
things. Does this work for you?
Thanks for fixing all the mistakes I left :(
@@ -7925,22 +7925,19 @@ Specify the @var{file} for the parser fi
The other output files' names are constructed from @var{file} as
described under the @samp{-v} and @samp{-d} options.
[EMAIL PROTECTED] -g
[EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]
Presented like this, one cannot see that the argument is optional.
I would write
@item [EMAIL PROTECTED]
@itemx [EMAIL PROTECTED]
[EMAIL PROTECTED] -x
[EMAIL PROTECTED] [EMAIL PROTECTED]
@itemx [EMAIL PROTECTED]
Ditto.
Index: src/getargs.c
===================================================================
RCS file: /sources/bison/bison/src/getargs.c,v
retrieving revision 1.105
diff -p -u -r1.105 getargs.c
--- src/getargs.c 28 Feb 2008 16:01:16 -0000 1.105
+++ src/getargs.c 6 Mar 2008 02:13:23 -0000
@@ -252,7 +252,10 @@ Generate LALR(1) and GLR parsers.\n\
"), stdout);
fputs (_("\
-Mandatory arguments to long options are mandatory for short options
too.\n\
+Mandatory arguments to long options are mandatory for short options
too. The\n\
+same is true for optional arguments with one exception: unlike --
defines, -d\n\
+cannot take an argument since POSIX Yacc requires that -d can be
bundled with\n\
+other short options.\n\
"), stdout);
I would make the second sentence another fputs, to please the
translators. In particular if at some point we manage to
get rid of this exception.
