Fri 2003-02-14 22:41, Benny Pedersen (2:237/53) wrote to All:

 > gcc -I/home/xpoint/fido/include -I./h -c -s -O3 -march=i386 -mcpu=i686 
 > -fbounds-check -fomit-frame-pointer -fstrength-reduce -fPIC -Wall -Wall 
 > -pedantic -Wno-char-subscripts -DUNIX -DNOSEMAPHORES -c src/uuecode.c

For people using GNU C I highly recommend the -W option (in addition to
-Wall).  You'll pick up more warnings that way (the more the better).

For UNIX programmers I also highly recommend GNU indent, Splint, cscope and
possibly vidbg.

GNU indent: http://www.gnu.org/software/indent/indent.html

"Splint is a tool for statically checking C programs for security
vulnerabilities and coding mistakes. With minimal effort, Splint can be
used as a better lint. If additional effort is invested adding
annotations to programs, Splint can perform stronger checking than can be
done by any standard lint."

Splint: http://www.splint.org/

"Cscope is a developer's tool for browsing source code. It has an
impeccable Unix pedigree, having been originally developed at Bell Labs
back in the days of the PDP-11. Cscope was part of the official AT&T
Unix distribution for many years, and has been used to manage projects
involving 20 million lines of code!"

cscope: http://cscope.sourceforge.net/

"vidbg is a full screen, text mode wrapper around gdb. It is intended
to be a very lightweight source level debugger. All interaction with gdb is
through vi-like keystrokes."

vidbg: http://www.tildeslash.org/vidbg.html

-- mail{at}ozzmosis.com

--- Msged/BSD 6.1.1