On Mon, 4 Dec 2006, Hans Aberg wrote:
> On 4 Dec 2006, at 20:01, Joel E. Denny wrote:
>
> > Well, maybe I'm wasting your time, but I hope that helps you to get a
> > better feel for the names than my original post did.
>
> I think you need to explain these much better, simply because wordings li
On Mon, 4 Dec 2006, Hans Aberg wrote:
> The problem is that different languages use different paradigms, and it m,ay
> not be possible to do this stuff in that context then.
Until we know what those languages are, I'm not sure how to handle them.
> It might work for
> parser specific features, b
On 4 Dec 2006, at 20:01, Joel E. Denny wrote:
Well, maybe I'm wasting your time, but I hope that helps you to get a
better feel for the names than my original post did.
I think you need to explain these much better, simply because
wordings like "this is the right place to put stuff like" is
On 4 Dec 2006, at 19:33, Joel E. Denny wrote:
, but if your design is still flexible, I'd suggest
using names that are more obvious about where the code will be
generated. For example:
%header{...}
%both{...}
Or maybe:
%declare{...}
%define{...}
%both{...}
In test release 2.3a, the directi
On Mon, 4 Dec 2006, Joel E. Denny wrote:
> > , but if your design is still flexible, I'd suggest
> > using names that are more obvious about where the code will be
> > generated. For example:
Although you can read about this in the NEWS entry for 2.3a, there's a
caveat you should be aware of if
On Mon, 4 Dec 2006, Jeff Inman wrote:
> > I meant to ask: does this sound like it will address your needs?
>
> Thanks for your reply. Yes, these sound like they will more than
> solve my problem. I can use a manual (and your message) to help
> me remember which is which
Currently in CVS, I've
On Dec 2, 2006, at 2:11 PM, Joel E. Denny wrote:
On Sat, 2 Dec 2006, Joel E. Denny wrote:
On Fri, 1 Dec 2006, Jeff Inman wrote:
It seems wrong to me that the second set of "%{ ... %}", after a
"%union{
...}", should insert
into the tab.cpp file, instead of into the tab.hpp file. I want
Hi all,
When generating C++, If I don't use %locations, why do I still get a
locations and position files? Are they required anyway? Moreover,
error in parser class still gets a reference to a location. If I don't
use locations, what reference is that? I would expect when disabling
locations that
