| From: | Grzegorz Jaskiewicz <gj(at)pointblue(dot)com(dot)pl> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Silence compiler warning about ignored return value. |
| Date: | 2008-11-20 15:40:39 |
| Message-ID: | E58F9DD0-8035-428B-BE57-D050CDDF7580@pointblue.com.pl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 2008-11-20, at 15:29, Peter Eisentraut wrote:
>
> Well, the warning is explicitly put in there for this specific
> function because you are supposed to process the return value. I'm
> sure a more smarter compiler would even warn "variable is assigned a
> value that is never used". ;-) (Note that gcc in general doesn't
> work about unused return values, only for those functions that glibc
> explicitly marks as candidates.)
afaik you need to use -Wall and -O3 to get that type of warning with 4.3
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2008-11-20 16:35:58 | Re: pgsql: Make SELECT FOR UPDATE/SHARE work on inheritance trees, by having |
| Previous Message | Magnus Hagander | 2008-11-20 15:39:32 | Re: Re: [COMMITTERS] pgsql: Silence compiler warning about ignored return value. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-11-20 15:50:32 | Re: pg_upgrade: How to deal with toast |
| Previous Message | Magnus Hagander | 2008-11-20 15:39:32 | Re: Re: [COMMITTERS] pgsql: Silence compiler warning about ignored return value. |