Request a Demo
Home   >   mailing lists

Re: Use pg_icu_unicode_version(void) instead of pg_icu_unicode_version() - Mailing list pgsql-hackers

From Andreas Karlsson
Subject Re: Use pg_icu_unicode_version(void) instead of pg_icu_unicode_version()
Date
Msg-id b075ac34-11cb-4613-9721-9a5542c962fe@proxel.se
Whole thread Raw
In response to Re: Use pg_icu_unicode_version(void) instead of pg_icu_unicode_version()  (Joe Conway <mail@joeconway.com>)
List pgsql-hackers
Tree view 
On 2/27/26 3:58 PM, Joe Conway wrote:
> On 2/27/26 01:04, Chao Li wrote:
>> What I'm interested in is the broader policy: when reviewing
>> patches, if we encounter a foo() declaration, should we consistently
>> request a change to foo(void)? If yes, the standard should be
>> documented somewhere.
> 
> Perhaps here?
> 
> https://wiki.postgresql.org/wiki/Committing_checklist

Nah, I think we should just enable the warnings unless we have a good 
reason not to.

Andreas

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Reduce planning time for large NOT IN lists containing NULL
Next
From: jian he
Date:
Subject: Re: pg_dumpall --roles-only interact with other options