[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: %push-* -> %define push_pull
From: |
Joel E. Denny |
Subject: |
Re: %push-* -> %define push_pull |
Date: |
Sun, 28 Oct 2007 19:53:34 -0400 (EDT) |
On Sun, 28 Oct 2007, Joel E. Denny wrote:
> > > > >> > %define api.pure "true||false"
>
> Will work on this soon.
Hi Paolo. I see that the Java skeleton depends on b4_pure_if in one
place:
/**
* Entry point for the scanner. Returns the token identifier corresponding
* to the next token and ]b4_pure_if([prepares to return], [stores])[
* the semantic value]b4_locations_if([ and beginning/ending positions])[
* of the token.
* @@return the token identifier corresponding to the next token. */
int yylex () ]b4_maybe_throws([b4_lex_throws])[;
Aren't Java interfaces always pure? That is, it seems that the user
should be warned that `%define api.pure' has no effect for Java.