[Top][All Lists]

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

Re: [PATCH] Factor %FLAG at scan level.

From: Joel E. Denny
Subject: Re: [PATCH] Factor %FLAG at scan level.
Date: Fri, 10 Apr 2009 14:35:59 -0400 (EDT)

On Fri, 10 Apr 2009, Akim Demaille wrote:

> > > > I would prefer:
> > > > 
> > > > api.lex-symbol
> > > 
> > > I really am not happy with "lex-symbol", but if you can't do better, I
> > > certainly can't :)
> > 
> > Other than the new prefix, I have nothing so far.
> Or maybe we should use the value, like you did for the api.  As you noted, it
> doesn't make sense with other api related things, such as %pure.  %define
> lex.api symbol|pure|global?  Or api.lex.

I like api.lex.  However, both "symbol" and "pure" are pure cases, so the 
names don't convey the distinction.  Maybe:

  %define api.lex-token "global|args|return"

That is, we're specifying how lex communicates its token.  Although this 
looks reasonable to me, it's low-level.  It doesn't emphasize the 
high-level advantages. Maybe:

  %define api.purity "impure|args|symbol"

So, it's the mechanism of purity.  Rather than saying "global" ("global 
purity" sounds like a good thing), we just emphasize that there isn't 
purity by saying "impure".

Maybe the best solution is a combination of these approaches.

Anyway, it looks like api.pure in its current form will have a short life 

reply via email to

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