Re: 2x compile warning

From: Kris Jurka <books(at)ejurka(dot)com>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: Gevik Babakhani <pgdev(at)xs4all(dot)nl>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 2x compile warning
Date: 2006-04-24 21:02:30
Message-ID: Pine.BSO.4.63.0604241601110.30903@leary2.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2006-04-24 21:12:49 Re: pgsql: Improve our private implementation of cbrt() to give results of
Previous Message Martijn van Oosterhout 2006-04-24 20:37:58 Re: 2x compile warning