[Top][All Lists]

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

Re: Enhancement request: enabling Variant in C parsers

From: Akim Demaille
Subject: Re: Enhancement request: enabling Variant in C parsers
Date: Sat, 25 Aug 2018 08:10:03 +0200

> Le 23 août 2018 à 14:09, Hans Åberg <address@hidden> a écrit :
>> On 23 Aug 2018, at 13:14, Akim Demaille <address@hidden> wrote:
>>> Le 23 août 2018 à 10:34, Hans Åberg <address@hidden> a écrit :
>>> This style with local.mk perhaps comes from an age where Automake was not 
>>> as smart. I use a Makefile.am.
>> Totally unrelated.  I use local.mk (should be local.am) because it’s
>> included from the top-level Makefile.am.  There’s a single Makefile
>> in the end, and that’s on purpose.  I do not want recursive Makefiles.
> Why not? I use local.mk, too, in simple cases.

Look for « recursive make considered harmful », there are tons of
pages about that.

>>> In addition, it might benefit from using say a 
>>> #define YYSTYPE double
>>> to illustrate how one sets ones own type.
>> What example are you referring to?  Also, you may have noticed that
>> I try to avoid using the preprocessor in favor of Bison directives.
> For the example, you do not set the type explicitly, so it ends up as a 
> default, so those that want to change need to go to the manual for that.

No, the type is explicitly set.  Just check it.

>>> so perhaps it should be replaced with a 
>>> %semantic-type {...}
>>> or something.
>> ‘something’ is '%define api.value.type'.
> So use it in the example, simply for illustration of the feature.

The example uses it, for variants.

reply via email to

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