Re: Bison GLR buffer-overflow and invalid pointer fixes

[Paul Eggert]

address@hidden writes:

> The new macro YYSIZEMAX is using size_t.

That's OK in glr.c, because glr.c is already using size_t elsewhere.

glr.c is not as fastidious about namespace cleanliness as yacc.c is.
Perhaps it should be, but it'd be some work to change this, and I'd
say it's lower priority than a lot of other things are.  Do we really
care that user code can't use the top-level symbol "size_t" to mean
something other than the size type?