gram: correct token numbering in precedence declarations

[bison.git] / tests / sets.at

diff --git a/tests/sets.at b/tests/sets.at
index 89519c3dc9c807a058e5e6095835e0644e410d39..fadbe6871210bdb0002e56a7838d273592230d17 100644 (file)
--- a/tests/sets.at
+++ b/tests/sets.at
@@ -1,6 +1,6 @@
 # Exercising Bison Grammar Sets.                      -*- Autotest -*-
 
-# Copyright (C) 2001-2002, 2005, 2007, 2009-2012 Free Software
+# Copyright (C) 2001-2002, 2005, 2007, 2009-2013 Free Software
 # Foundation, Inc.
 
 # This program is free software: you can redistribute it and/or modify
@@ -86,7 +86,7 @@ AT_CHECK([[cat sets]], [],
       0  e $end
   e derives
       1  'e'
-      2  /* empty */
+      2  %empty
 NULLABLE
   $accept: no
   e: yes
@@ -100,10 +100,10 @@ FDERIVES
   $accept derives
       0  e $end
       1  'e'
-      2  /* empty */
+      2  %empty
   e derives
       1  'e'
-      2  /* empty */
+      2  %empty
 ]])
 
 AT_CLEANUP
@@ -113,7 +113,7 @@ AT_CLEANUP
 ## Broken Closure.  ##
 ## ---------------- ##
 
-# TC was once broken during a massive `simplification' of the code.
+# TC was once broken during a massive 'simplification' of the code.
 # It resulted in bison dumping core on the following grammar (the
 # computation of FIRSTS uses TC).  It managed to produce a pretty
 # exotic closure:
@@ -263,7 +263,7 @@ AT_CLEANUP
 # In some weird cases Bison could compute an incorrect final state
 # number.  This happens only if the $end token is used in the user
 # grammar, which is a very suspicious accidental feature introduced as
-# a side effect of allowing the user to name $end using `%token END 0
+# a side effect of allowing the user to name $end using '%token END 0
 # "end of file"'.
 
 AT_SETUP([Accept])