Re: Make foo=null a warning by default. - Mailing list pgsql-hackers

From David Fetter
Subject Re: Make foo=null a warning by default.
Date
Msg-id 20180719055217.GA29917@fetter.org
Whole thread Raw
In response to Re: Make foo=null a warning by default.  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: Make foo=null a warning by default.  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
On Wed, Jul 18, 2018 at 04:15:30PM -0400, Fabien COELHO wrote:
> 
> >[...] Done.
> 
> All looks well, but I just noticed a warning:
> 
>  gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels
-Wmissing-format-attribute-Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard
-Wno-format-truncation-O2 -I. -I. -I../../../../src/include  -D_GNU_SOURCE   -c -o guc.o guc.c
 
>  guc.c:4090:3: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types]
>    &transform_null_equals,
>    ^
>  guc.c:4090:3: note: (near initialization for ‘ConfigureNamesEnum[16].variable’)
> 
> Too bad, gcc does not like an (enum*) there. Maybe cast to (int *), or
> declare the variable as an int (which seems to be what is done for others)?

Done that way.

Best,
David.
-- 
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: More consistency for some file-related error message
Next
From: Michael Paquier
Date:
Subject: Re: print_path is missing GatherMerge and CustomScan support