zen blog

Main menu

Calendar

« February 2006 »
Mon	Tue	Wed	Thu	Fri	Sat	Sun
		1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28

Search

Last Comments

Feeds

« Ubuntu Desktop News, second issue | Setting GNOME goals (or the story of my secret »

Sunday 12 February 2006

The endless -Werror debate

Davyd: no need to copy all this complex autofoo stuff in your configure.in. Just use gnome-common and put GNOME_COMPILE_WARNINGS(yes) in your configure.in.

I tend to agree that a maintainer should use -Werror if available since it helps catch some nasty bugs. Forcing everyone to use it is another thing.

[11:53] | [GNOME] | [#360] | [feed]

Trackbacks

No trackback.

To add a trackback for this post: http://www.vuntz.net/journal/trackback/360

Comments

1. Davyd [12/02/2006@12:53] [reply]

Doesn't GNOME_COMPILE_WARNINGS do something different?

2. Vincent [12/02/2006@13:04] [reply]

Davyd: it adds this:

--enable-compile-warnings=[no/minimum/yes/maximum/error]
Turn on compiler warnings

3. MadCoder [12/02/2006@13:20] [reply]

Every one should compile C (no joke inside) with at least :

-Wall -Wextra (or -W for older compilers) -Werror

I also use on every project :

-fstrict-aliasing -Wshadow -Wcast-align -Wwrite-strings -Wsign-compare -Wno-uninitialized -Wpointer-arith -Wredundant-decls -Wbad-function-cast -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs

and also when I have not too many function pointers with unused parameters, also :
-Wno-unused (helps to keep track of old variable you no longer use, and that you can also clean).

Every one should do that. C is a sharp tool, one should not *hope* it works, and keep every chances on his side.

4. MadCoder [12/02/2006@13:21] [reply]

hey, I meant no -Wno-[...] but the -W[...] settings.