Files
bison/data/skeletons
Akim Demaille d4a6c3c58a c++: beware of short ranges for state numbers
Now that we use small integral types, possibly unsigned (e.g.,
unsigned char), to store state numbers, using -1 to denote an empty
state (i.e., a state that stores no semantical value) is very
dangerous: it will be confused with state 255, which might be
non-empty.

Rather than allocating a larger range of state numbers to keep the
empty-state apart, let's use the number of a state known to store no
value.  The initial state, numbered 0, seems to fit perfectly the job.

Reported by Frank Heckenbach.
https://lists.gnu.org/archive/html/bug-bison/2019-11/msg00016.html

* data/skeletons/lalr1.cc (empty_state): Be 0.
2019-12-07 09:22:55 +01:00
..
2019-12-02 19:35:01 +01:00
2019-01-05 14:58:05 +01:00
2019-01-05 14:58:05 +01:00
2019-01-05 14:58:05 +01:00
2019-12-01 10:05:48 +01:00
2019-01-05 14:58:05 +01:00
2019-06-23 11:20:18 +02:00
2019-11-02 16:40:50 +01:00
2019-01-05 14:58:05 +01:00
2019-06-19 19:15:31 +02:00
2019-11-02 16:40:50 +01:00
2019-01-05 14:58:05 +01:00