🚀 go-pugleaf

lwv26@cas.org (Larry W. Virden) writes:

>I would love to have a way to call gcc with some 'noise' flags to tell gcc
>to do lots of error checking but to produce no .o or a.out type file.
>
>I would like to have at least -Wall -pedantic -traditional (or -ansi) and
>if there are a few other good 'noise' flags that would be great.  Note
>that I DO want to know though if the arguments are mismatched between
>modules - does that require me to produce .o files?  If so, can I tell
>gcc to put them in some other directory?

You can use the -fsyntax-only option to suppress creating of an object
file, but I don't know if that also suppresses some warnings.
To get warning about uninitialized variables, you have to compile with -O.
In addition to -ansi -pedantic -Wall, I use the following options:
	-Wshadow -Wwrite-strings -Wcast-qual
	-Wtraditional -Wcast-align -Wstrict-prototypes -Wmissing-prototypes
	-Wenum-clash -Woverloaded-virtual	# C++ options

Check the man page.

-- 
Fergus Henderson                     This .signature virus might be
fjh@munta.cs.mu.OZ.AU                getting old, but you still can't
                                     consistently believe it unless you
Linux: Choice of a GNU Generation    copy it to your own .signature file!