Re: Using defines for protocol characters
Dave Cramer <davecramer@gmail.com>
From: Dave Cramer <davecramer@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Peter Smith <smithpb2250@gmail.com>, Tatsuo Ishii <ishii@sraoss.co.jp>, pgsql-hackers@lists.postgresql.org, nathandbossart@gmail.com
Date: 2023-08-07T20:00:25Z
Lists: pgsql-hackers
On Mon, 7 Aug 2023 at 12:59, Robert Haas <robertmhaas@gmail.com> wrote: > On Mon, Aug 7, 2023 at 2:25 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > +1. For ease of greppability, maybe even PQMSG_EmptyQueryResponse > > and so on? Then one grep would find both uses of the constants and > > code/docs references. Not sure if the prefix should be all-caps or > > not if we go this way. > > PqMsgEmptyQueryResponse or something like that seems better, if we > want to keep the current capitalization. I'm not a huge fan of the way > we vary our capitalization conventions so much all over the code base, > but I think we would at least do well to keep it consistent from one > end of a certain identifier to the other. > I don't have a strong preference, but before I make the changes I'd like to get consensus. Can we vote or whatever it takes to decide on a naming pattern that is acceptable ? Dave
Commits
-
Introduce macros for protocol characters.
- f4b54e1ed985 17.0 landed
-
Remove configure check for z_streamp
- eeb4eeea2c52 17.0 cited