bison-patches
[Top][All Lists]
Advanced

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

[PATCH] YYERRCODE.


From: Akim Demaille
Subject: [PATCH] YYERRCODE.
Date: Thu, 13 Nov 2008 06:01:44 -0000

        * TODO (YYERRCODE): Mention the case of $undef.
---
 ChangeLog |    5 +++++
 TODO      |   23 +++++++++++++++++++++++
 2 files changed, 28 insertions(+), 0 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 8abd8ce..48808a5 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,10 @@
 2008-11-13  Akim Demaille  <address@hidden>
 
+       YYERRCODE.
+       * TODO (YYERRCODE): Mention the case of $undef.
+
+2008-11-13  Akim Demaille  <address@hidden>
+
        TODO: YYPRINT.
        * TODO (YYPRINT): New.
 
diff --git a/TODO b/TODO
index 0a4aef4..e42c4b5 100644
--- a/TODO
+++ b/TODO
@@ -14,6 +14,29 @@ number for the error token, which POSIX wants to be 256, but 
which
 Bison might renumber if the user used number 256.  Keep fix and doc?
 Throw away?
 
+We could (should?) also treat the case of the undef_token, which is
+numbered 257 for yylex, and 2 internal.  Both appear for instance in
+toknum:
+
+  const unsigned short int
+  parser::yytoken_number_[] =
+  {
+       0,   256,   257,   258,   259,   260,   261,   262,   263,   264,
+
+while here
+
+   enum yytokentype {
+     TOK_EOF = 0,
+     TOK_EQ = 258,
+
+so both 256 and 257 are "mysterious".
+
+  const char*
+  const parser::yytname_[] =
+  {
+  "\"end of command\"", "error", "$undefined", "\"=\"", "\"break\"",
+
+
 ** YYFAIL
 It is seems to be *really* obsolete now, shall we remove it?
 
-- 
1.6.0.2.588.g3102





reply via email to

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