[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: quick bison Q

From: Akim Demaille
Subject: Re: quick bison Q
Date: Sun, 05 Jan 2003 15:01:47 +0100
User-agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i386-pc-linux-gnu)

| > Date: Mon, 09 Dec 2002 10:26:37 -0600
| > From: David Durham <address@hidden>
| > 
| > I really don't think that bison should have to worry about what they
| > mean.  It could just find what's between the union keyword and the
| > {, remove all the whitespace from that sequence of chars and define
| > that as the character sequence of the typename for the union.
| I suppose that is what Bison will have to do.  What a pain.

Bison should not be too kind here, again.  In particular because in
C++ you are not free on the name you gave to the union: it must be
that of the typedef (there are not several name spaces: union, class,
struct and types are in the same name space).  Users should not rely
on such a ``feature'', imho.

It also collides with future extensions, such as multiple %union.

Therefore, I would look for other means to satisfy the needs of the
users, but not that one.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]