From: Akim Demaille <akim@epita.fr>
Date: Wed, 10 Apr 2002 11:03:39 +0000 (+0000)
Subject: More ideas.
X-Git-Tag: BISON-1_49a~45
X-Git-Url: https://git.saurik.com/bison.git/commitdiff_plain/eaff5ee3c5c3eeaa4b5c94efc900a27bf42330a4?ds=inline

More ideas.
---

diff --git a/TODO b/TODO
index 0e385ebc..cfbca2a0 100644
--- a/TODO
+++ b/TODO
@@ -1,5 +1,38 @@
 -*- outline -*-
 
+* Coding system independence
+Paul notes: 
+
+	Currently Bison assumes 8-bit bytes (i.e. that UCHAR_MAX is
+	255).  It also assumes that the 8-bit character encoding is
+	the same for the invocation of 'bison' as it is for the
+	invocation of 'cc', but this is not necessarily true when
+	people run bison on an ASCII host and then use cc on an EBCDIC
+	host.  I don't think these topics are worth our time
+	addressing (unless we find a gung-ho volunteer for EBCDIC or
+	PDP-10 ports :-) but they should probably be documented
+	somewhere.
+
+* Using enums instead of int for tokens.
+Paul suggests:
+
+   #ifndef YYTOKENTYPE
+   # if defined (__STDC__) || defined (__cplusplus)
+      /* Put the tokens into the symbol table, so that GDB and other debuggers
+         know about them.  */
+      enum yytokentype {
+        FOO = 256,
+        BAR,
+        ...
+      };
+      /* POSIX requires `int' for tokens in interfaces.  */
+   #  define YYTOKENTYPE int
+   # endif
+   #endif
+   #define FOO 256
+   #define BAR 257
+   ...
+
 * Unit rules
 Maybe we could expand unit rules, i.e., transform