bison-patches
[Top][All Lists]
Advanced

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

doc: sort the warning categories


From: Akim Demaille
Subject: doc: sort the warning categories
Date: Sun, 21 Apr 2019 16:49:39 +0200

commit dff7454371003ddce2d6b07d940f965c896d8b81
Author: Akim Demaille <address@hidden>
Date:   Sat Apr 6 09:32:10 2019 +0200

    doc: sort the warning categories
    
    * doc/bison.texi, src/getargs.c: here.

diff --git a/doc/bison.texi b/doc/bison.texi
index 0531c526..41e75d28 100644
--- a/doc/bison.texi
+++ b/doc/bison.texi
@@ -10349,6 +10349,23 @@ is specified.
 Output warnings falling in @var{category}.  @var{category} can be one
 of:
 @table @code
address@hidden conflicts-sr
address@hidden conflicts-rr
+S/R and R/R conflicts.  These warnings are enabled by default.  However, if
+the @code{%expect} or @code{%expect-rr} directive is specified, an
+unexpected number of conflicts is an error, and an expected number of
+conflicts is not reported, so @option{-W} and @option{--warning} then have
+no effect on the conflict report.
+
address@hidden deprecated
+Deprecated constructs whose support will be removed in future versions of
+Bison.
+
address@hidden empty-rule
+Empty rules without @code{%empty}.  @xref{Empty Rules}.  Disabled by
+default, but enabled by uses of @code{%empty}, unless
address@hidden was specified.
+
 @item midrule-values
 Warn about midrule values that are set but not used within any of the actions
 of the parent rule.
@@ -10369,26 +10386,6 @@ These warnings are not enabled by default since they 
sometimes prove to
 be false alarms in existing grammars employing the Yacc constructs
 @code{$0} or @address@hidden (where @var{n} is some positive integer).
 
address@hidden yacc
-Incompatibilities with POSIX Yacc.
-
address@hidden conflicts-sr
address@hidden conflicts-rr
-S/R and R/R conflicts.  These warnings are enabled by default.  However, if
-the @code{%expect} or @code{%expect-rr} directive is specified, an
-unexpected number of conflicts is an error, and an expected number of
-conflicts is not reported, so @option{-W} and @option{--warning} then have
-no effect on the conflict report.
-
address@hidden deprecated
-Deprecated constructs whose support will be removed in future versions of
-Bison.
-
address@hidden empty-rule
-Empty rules without @code{%empty}.  @xref{Empty Rules}.  Disabled by
-default, but enabled by uses of @code{%empty}, unless
address@hidden was specified.
-
 @item precedence
 Useless precedence and associativity directives.  Disabled by default.
 
@@ -10450,6 +10447,9 @@ One would get the exact same parser with the following 
directives instead:
 @end group
 @end example
 
address@hidden yacc
+Incompatibilities with POSIX Yacc.
+
 @item other
 All warnings not categorized above.  These warnings are enabled by default.
 
diff --git a/src/getargs.c b/src/getargs.c
index 8673d41c..2a0493a1 100644
--- a/src/getargs.c
+++ b/src/getargs.c
@@ -335,13 +335,13 @@ Output:\n\
 
       fputs (_("\
 Warning categories include:\n\
-  'midrule-values'    unset or unused midrule values\n\
-  'yacc'              incompatibilities with POSIX Yacc\n\
   'conflicts-sr'      S/R conflicts (enabled by default)\n\
   'conflicts-rr'      R/R conflicts (enabled by default)\n\
   'deprecated'        obsolete constructs\n\
   'empty-rule'        empty rules without %empty\n\
+  'midrule-values'    unset or unused midrule values\n\
   'precedence'        useless precedence and associativity\n\
+  'yacc'              incompatibilities with POSIX Yacc\n\
   'other'             all other warnings (enabled by default)\n\
   'all'               all the warnings except 'yacc'\n\
   'no-CATEGORY'       turn off warnings in CATEGORY\n\




reply via email to

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