[Top][All Lists]

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

Re: Enhancement request: enabling Variant in C parsers

From: Hans Åberg
Subject: Re: Enhancement request: enabling Variant in C parsers
Date: Sat, 25 Aug 2018 14:48:37 +0200

> On 25 Aug 2018, at 07:50, Akim Demaille <address@hidden> wrote:
>> Le 23 août 2018 à 18:23, Hans Åberg <address@hidden> a écrit :
>>> On 23 Aug 2018, at 13:14, Akim Demaille <address@hidden> wrote:
>>> ‘something’ is '%define api.value.type'.
>> When used, the macro still overrides it, which might cause confusion if one 
>> happens to use both (like the old definition happens to linger). That is,
>> %define api.value.type {a_type}
>> produces in .hh parser class:
>> #ifndef YYSTYPE
>>   /// Symbol semantic values.
>>   typedef a_type semantic_type;
>> #else
>>   typedef YYSTYPE semantic_type;
>> #endif
> I don’t think it’s too much of a problem, and it’s going to be
> painful to handle.  If you think it is worth it, please submit a patch :)

You are the man. But I just found it confusing when doing the change to the new 

reply via email to

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