[Top][All Lists]

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

Re: glr: include the created header

From: Joel E. Denny
Subject: Re: glr: include the created header
Date: Wed, 21 Dec 2005 21:12:25 -0500 (EST)

On Mon, 19 Dec 2005, Joel E. Denny wrote:

> Another possibility is to require the user to handle %union dependencies 
> himself.  I often #define YYSTYPE in a YYSTYPE.h that contains its 
> dependencies.  I then #include YYSTYPE.h in a literal block.  In the 
> scanner, I #include YYSTYPE.h and  This is the only way to 
> handle non-trivial YYLTYPE definitions right now anyway, right?

To clarify that last sentence: I think you agreed that the absence of a 
%union should mean that no literal blocks are placed in the header.  This 
would mean that a user could not specify that his own YYLTYPE definition 
be placed in the header.

To accommodate YYSTYPE dependencies, YYLTYPE dependencies, a non-%union 
YYSTYPE definition, a user YYLTYPE definition, or anything else the user 
might wish to place in the header, perhaps there should be some sort of 
general `header' qualifier for any literal block:

    /* C code */


reply via email to

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