1 |
-*- outline -*- |
-*- outline -*- |
2 |
|
|
3 |
|
* Coding system independence |
4 |
|
Paul notes: |
5 |
|
|
6 |
|
Currently Bison assumes 8-bit bytes (i.e. that UCHAR_MAX is |
7 |
|
255). It also assumes that the 8-bit character encoding is |
8 |
|
the same for the invocation of 'bison' as it is for the |
9 |
|
invocation of 'cc', but this is not necessarily true when |
10 |
|
people run bison on an ASCII host and then use cc on an EBCDIC |
11 |
|
host. I don't think these topics are worth our time |
12 |
|
addressing (unless we find a gung-ho volunteer for EBCDIC or |
13 |
|
PDP-10 ports :-) but they should probably be documented |
14 |
|
somewhere. |
15 |
|
|
16 |
|
* Using enums instead of int for tokens. |
17 |
|
Paul suggests: |
18 |
|
|
19 |
|
#ifndef YYTOKENTYPE |
20 |
|
# if defined (__STDC__) || defined (__cplusplus) |
21 |
|
/* Put the tokens into the symbol table, so that GDB and other debuggers |
22 |
|
know about them. */ |
23 |
|
enum yytokentype { |
24 |
|
FOO = 256, |
25 |
|
BAR, |
26 |
|
... |
27 |
|
}; |
28 |
|
/* POSIX requires `int' for tokens in interfaces. */ |
29 |
|
# define YYTOKENTYPE int |
30 |
|
# endif |
31 |
|
#endif |
32 |
|
#define FOO 256 |
33 |
|
#define BAR 257 |
34 |
|
... |
35 |
|
|
36 |
* Unit rules |
* Unit rules |
37 |
Maybe we could expand unit rules, i.e., transform |
Maybe we could expand unit rules, i.e., transform |
38 |
|
|