public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Harjyot Bagga <[email protected]>
Cc: Aleksander Alekseev <[email protected]>
Cc: [email protected]
Subject: Re: Grammar guidelines in Postgres
Date: Thu, 04 Jul 2024 12:01:55 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+FYKR-NVQ3tWhBroCeqBLPHzjEjUGUrCWA=_Yxcs6mWFm-7oQ@mail.gmail.com>
References: <CA+FYKR-ogq6WnLtc2bKvFx5qr7UK0aYUssowb=F_zOxD0uDFXQ@mail.gmail.com>
<CAJ7c6TPUuwEE-Nxr=KF_ziS1nNPmKQx0Vwu1MCMHjBVPV4bWKw@mail.gmail.com>
<CA+FYKR-NVQ3tWhBroCeqBLPHzjEjUGUrCWA=_Yxcs6mWFm-7oQ@mail.gmail.com>
Harjyot Bagga <[email protected]> writes:
> One such suggestion or rule for example is the Postgres does not support
> Postfix operators. So whenever a new feature is introduced developers make
> sure that they do not add a postfix operators in their grammar. Just like
> that are there any other further rules or suggestions compiled by post
> hackers and maintainers?
[ shrug... ] If you try to re-introduce postfix operators you'll get
a ton of shift-reduce conflicts. We have a hard rule that such
conflicts are not allowed, even though Bison can be told to ignore
them. Beyond that, there's not much.
regards, tom lane
view thread (2+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Grammar guidelines in Postgres
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox