Re: pgsql: Silence compiler warning on win32.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Silence compiler warning on win32.
Date: 2009-01-27 16:07:35
Message-ID: 15865.1233072455@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> Tom Lane wrote:
>> Surely this patch is wrong. It is suppressing, not fixing, a critical
>> warning about a datatype mismatch.

> You mean the signed vs unsigned part? Other than that, int and dword are
> always the same on win32...

Hmm, need more caffeine I guess. I was thinking dword == long. But in
any case, I'd feel a lot more comfortable if the patch ifdef'd the
declaration of exit_status to match, rather than forcing a cast of the
pointer value. Just a couple weeks ago I wasted a great deal of time
finding a bug that was created by someone overriding this exact type of
compiler warning with a cast to something that *wasn't* binary
compatible. (It worked fine on the author's machine, of course, but
not so much on one with a different sizeof long...)

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2009-01-27 20:24:18 Re: [COMMITTERS] pgsql: Automatic view update rules Bernd Helmle
Previous Message Magnus Hagander 2009-01-27 15:39:56 Re: pgsql: Silence compiler warning on win32.

Browse pgsql-hackers by date

  From Date Subject
Next Message Gregory Stark 2009-01-27 16:16:22 Re: More FOR UPDATE/FOR SHARE problems
Previous Message Joshua D. Drake 2009-01-27 16:04:22 Re: pg_upgrade project status