From fc2476c7cd70ff882dd29058d0fd6440972a6c64 Mon Sep 17 00:00:00 2001
From: Akim Demaille <demaille@gostai.com>
Date: Fri, 29 Aug 2008 20:29:20 +0200
Subject: [PATCH] YYERRCODE.

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

diff --git a/ChangeLog b/ChangeLog
index 8abd8ce8..48808a51 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2008-11-13  Akim Demaille  <demaille@gostai.com>
+
+	YYERRCODE.
+	* TODO (YYERRCODE): Mention the case of $undef.
+
 2008-11-13  Akim Demaille  <demaille@gostai.com>
 
 	TODO: YYPRINT.
diff --git a/TODO b/TODO
index 0a4aef40..e42c4b5c 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?
 
-- 
2.45.2