Prev: pg_start_backup and pg_stop_backup Re: [HACKERS] Re:[COMMITTERS] pgsql: Make CheckRequiredParameterValues() depend upon correct
Next: pg_start_backup and pg_stop_backup Re: [HACKERS] Re:[COMMITTERS] pgsql: Make CheckRequiredParameterValues() depend uponcorrect
From: Tom Lane on 28 Apr 2010 14:34
"Kevin Grittner" <Kevin.Grittner(a)wicourts.gov> writes:
> I'm wondering the reason that I see (void *) casts for function call
> parameters which are pointers to specific structures. Do some
> compilers generate warnings if these are omitted?

There are some places where we do that to suppress warnings, yes.
Any particular place where you think it's unnecessary?

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: "Kevin Grittner" on 28 Apr 2010 14:39
Tom Lane <tgl(a)sss.pgh.pa.us> wrote:

> Any particular place where you think it's unnecessary?

How about the 2nd (tag pointer) parameter for hash_search?

-Kevin

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: pg_start_backup and pg_stop_backup Re: [HACKERS] Re:[COMMITTERS] pgsql: Make CheckRequiredParameterValues() depend upon correct
Next: pg_start_backup and pg_stop_backup Re: [HACKERS] Re:[COMMITTERS] pgsql: Make CheckRequiredParameterValues() depend uponcorrect