Domingo Alvarez Duarte writes:
> What if the generated parser/lexer be present in the tarball distributions ?
It is. The discussion here is about developer convenience (how painful
is it to read or modify a rule) versus developer convenience (what hoops
have you got to jump through to install a
I understand the concerns but I would not qualify it as "minor
developer-convenience feature".
I'm not impartial because the initial suggestion was mine, just to add
more options to be considered:
What if the generated parser/lexer be present in the tarball distributions ?
Cheers !
On 7/7/2
ilm...@ilmari.org (Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?=) writes:
> Peter Eisentraut writes:
>> On 04.07.21 17:58, Tom Lane wrote:
>>> When is "some time now"?
>> release 2.5 (2011-05-14)
> Do we support building on RHEL6? It only ships bison 2.4, so that would
> mean people building on that
Peter Eisentraut writes:
> On 04.07.21 17:58, Tom Lane wrote:
>> Domingo Alvarez Duarte writes:
>>> Here https://gist.github.com/mingodad/49291e0e9505522c66fcd3fcea4a939d I
>>> posted the postgresql-13.3/src/backend/parser/gram.y with positional
>>> references by named references that is support
On 04.07.21 17:58, Tom Lane wrote:
Domingo Alvarez Duarte writes:
Here https://gist.github.com/mingodad/49291e0e9505522c66fcd3fcea4a939d I
posted the postgresql-13.3/src/backend/parser/gram.y with positional
references by named references that is supported by bison for some time now.
When is
Domingo Alvarez Duarte writes:
> Here https://gist.github.com/mingodad/49291e0e9505522c66fcd3fcea4a939d I
> posted the postgresql-13.3/src/backend/parser/gram.y with positional
> references by named references that is supported by bison for some time now.
When is "some time now"?
Currently, we
