Hans Åberg wrote:
> > On 17 Dec 2018, at 19:09, Frank Heckenbach wrote:
>
> [Note: you don't cc me, only others, for some reason.]
By default, I keep recipients (list) and CCs (Akim) as is. If you
want a private copy, set a Reply-To.
> > so:
> >
> >> Actually, I pass the semantic value throug
> On 18 Dec 2018, at 13:20, Frank Heckenbach wrote:
>
> Hans Åberg wrote:
>
>>> On 17 Dec 2018, at 19:09, Frank Heckenbach wrote:
>>
>> [Note: you don't cc me, only others, for some reason.]
>
> By default, I keep recipients (list) and CCs (Akim) as is.
With a reply to all, it would come
On 2018-12-08 16:45, Askar Safin wrote:
Hi. Often the only thing I want to do in Bison is just generate AST
and nothing else. Unfortunately, in this case code becomes very
repetitive.
I think the generation of *parse trees* can be automated.
AST's omit information from (abstract away from) the
Bison 3.2.3 is a bug fix release of Bison 3.2.
Bison 3.2 brought massive improvements to the deterministic C++ skeleton,
lalr1.cc. When variants are enabled and the compiler supports C++11 or
better, move-only types can now be used for semantic values. C++98 support
is not deprecated. Please se
Hi Frank, Hi all,
> Le 16 déc. 2018 à 10:02, Frank Heckenbach a écrit :
>
> So to make it safe, we might need something like this:
>
> static inline
> symbol_type
> make_symbol (token_type type, b4_locations_if([const location_type& l, ])T&&
> v);
>
> auto-generated for each semantic type
