Re: 2x compile warning - Mailing list pgsql-hackers

From Kris Jurka
Subject Re: 2x compile warning
Date
Msg-id Pine.BSO.4.63.0604241601110.30903@leary2.csoft.net
Whole thread Raw
In response to Re: 2x compile warning  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: 2x compile warning  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: 2x compile warning  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers

On Mon, 24 Apr 2006, Martijn van Oosterhout wrote:

> Perhaps someone could check if changing the test explicitly check
> against NULL:
>
>>             ((attnum) > (int) (tup)->t_data->t_natts) ? \
>>             ( \
>>                 (((isnull) != NULL)? (*(isnull) = true) : (dummyret)NULL), \
>>                 (Datum)NULL \
>
> removes the warning. It seems silly for the GCC people to add warnings
> for this kind of stuff without a simple way to bypass it...

Yes, this coding removes the warning.

Kris Jurka



pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: 2x compile warning
Next
From: "Magnus Hagander"
Date:
Subject: Re: pgsql: Improve our private implementation of cbrt() to give results of