>Most modern compilers produce better warnings than lint anyway...
>presuming you use ANSI-stlye function prototypes and don't switch
>to K&R mode.
Ok specifically Gimpel Lint which picks up much more errors
than any compiler i`ve ever used..
Catches much more than bad prototypes.
charlie
On Mon, 1 Mar 1999, charlie wallace wrote:
> one comment to add
>
> Lint!!!
Most modern compilers produce better warnings than lint anyway...
presuming you use ANSI-stlye function prototypes and don't switch
to K&R mode.
Steve Baker(817)619-2657 (Vox/Vox-Mail)
Raytheon System
one comment to add
Lint!!!
8-)
>2. Compile with maximum warnings (gcc -ansi -pedantic -Wall).
> In src/FX/fxsetup.c I found a switch statement without a default
> case. I added a default no-op case. David, is that right or
> should an error be signaled?
I just compiled the latest sources and found a few things to mention.
1. When developing/debugging be sure to define the DEBUG symbol (with
-DDEBUG, for example). This detected an uninitialized entry in the
API function table.
2. Compile with maximum warnings (gcc -ansi -pedantic -Wall).
