[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: experimental features in Bison 2.3a+
From: |
Joel E. Denny |
Subject: |
Re: experimental features in Bison 2.3a+ |
Date: |
Wed, 6 Dec 2006 04:55:17 -0500 (EST) |
On Wed, 6 Dec 2006, Hans Aberg wrote:
> > For verbatim strings:
> >
> > %define "NAME" "STRING"
>
> No, just one line. This why <code> had to be added.
Do you have a specific need for multiline strings that are not parsed as
code?
> > For code that needs to be parsed:
> >
> > %define "NAME" { CODE }
> >
> > How does calling it %code in the second case solve the problem of multiple
> > languages?
>
> Because parsing of the code part needs to be changed according to language.
> For a macro define, that seems to be a poor practice.
So the issue isn't with multiple languages? It's with parsing CODE at all
when the directive is named %define?
This doesn't bother me. { CODE } is always parsed no matter where it
appears in the Bison grammar file.
Re: experimental features in Bison 2.3a+, Hans Aberg, 2006/12/03
Re: experimental features in Bison 2.3a+, Hans Aberg, 2006/12/04
- Re: experimental features in Bison 2.3a+, Joel E. Denny, 2006/12/04
- Re: experimental features in Bison 2.3a+, Hans Aberg, 2006/12/05
- Re: experimental features in Bison 2.3a+, Joel E. Denny, 2006/12/05
- Re: experimental features in Bison 2.3a+, Hans Aberg, 2006/12/06
- Re: experimental features in Bison 2.3a+,
Joel E. Denny <=
- Re: experimental features in Bison 2.3a+, Hans Aberg, 2006/12/06