[Top][All Lists]

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

Re: Manual changes for api.prefix

From: Akim Demaille
Subject: Re: Manual changes for api.prefix
Date: Sun, 15 Dec 2013 12:27:36 +0100

Le 13 déc. 2013 à 22:47, Arthur Schwarz <address@hidden> a écrit :

> Section 3.7.13 page 87
>    %define api.prefix {prefix} should be %define api.prefix prefix

No it should not.  However, users of Bison 2.7 should not read the
documentation of Bison 3.0.

>    Language C yy strings renamed
>    Language C++ namespaces in *.hh and *.cc renamed. yy strings unaffected.

Which is great for a language that supports namespaces.
What is exactly the problem you have?

>    Language Java can't get the fool thing to work.

What is your suggestion?  Of course, about 3.0.2, not about

> Section 3.8 page 94 
>   yytokentype missing from the enumeration.

I’ll have a look.

> I believe that 3.8 Multiple Parsers in Same Program only affects C and Java
> and C++ differently.

S/R conflict.  How should I read your «and»s?

> Most particularly in C++ and Java multiple instances of
> the same parser need no additional support, whereas in C they do. And in all
> the languages multiple different parsers need renaming, hence api.prefix,
> and should be separately mentioned. The title should reflect this
> distinction.

I’m sorry, but I don’t fully understand what you mean.
The whole Chapter 3 is focused on C, not C++ and Java.
What would you suggest that we do?

reply via email to

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