> Le 23 août 2018 à 18:23, Hans Åberg <[email protected]> a écrit :
> 
> 
>> On 23 Aug 2018, at 13:14, Akim Demaille <[email protected]> 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 :)

Reply via email to