Hey Tom,
> Le 22 mai 2019 à 23:25, Tom Lane a écrit :
>
> Akim Demaille writes:
>> Honestly, I seriously doubt that you have contributors that don't
>> have MacPorts or Brew installed, and both are pretty up to date on
>> Bison.
>
> Hm, well, I'm
hi Tom!
> Le 23 mai 2019 à 00:29, Tom Lane a écrit :
>
> Andrew Dunstan writes:
>> On 5/21/19 11:49 AM, Akim Demaille wrote:
>>> Usually users of Bison build tarballs with the generated parsers
>>> in them, and ship/test from that.
>
>> The buildfa
Tom,
> Le 23 mai 2019 à 06:00, Tom Lane a écrit :
>
> Robert Haas writes:
>> Another thing is that it would be nice to have a better way of
>> resolving conflicts than attaching precedence declarations. Some
>> problems can't be solved that way at all, and others can only be
>> solved that way
> Le 22 mai 2019 à 23:44, Daniel Gustafsson a écrit :
>
>> On 22 May 2019, at 23:25, Tom Lane wrote:
>>
>> Akim Demaille writes:
>>> Honestly, I seriously doubt that you have contributors that don't
>>> have MacPorts or Brew installed, and bot
Hi Tom,
> Le 21 mai 2019 à 21:06, Tom Lane a écrit :
>
> Akim Demaille writes:
>>> Le 20 mai 2019 à 15:54, Tom Lane a écrit :
>>> 2013? Certainly not. We have a lot of buildfarm critters running
>>> older platforms than that.
>
>> This I
Hi Tom!
> Le 20 mai 2019 à 15:54, Tom Lane a écrit :
>
> Akim Demaille writes:
>> It is for the same reasons that I would recommend not using associativity
>> directives (%left, %right, %nonassoc) where associativity plays no role:
>> %precedence is made for this
Hi Tom,
> Le 19 mai 2019 à 20:27, Tom Lane a écrit :
>
> Akim Demaille writes:
>> In the following two proposed patches, I remove directives that are
>> completely useless.
>
> I'm far from convinced that the proposed changes in gram.y are a good
> idea. B
n of Bison that is
required. Given that it's a maintainer-side tool, I would suggest targeting
recent versions of Bison, but opinions might differ here.
Cheers!
commit 75e597aa239d8ebc332d3a29630ecad0133d3d6f
Author: Akim Demaille
Date: Sun May 19 14:24:33 2019 +0200
json_
