Both ICC and Sun's lint are very good at finding variables that are
set but never used. The last batch of commits from me is all from
ICC's digging.
I'm working on quieting most of ICC's warnings, so that only the good
ones shine through. We'll have some tremendous tools at our disposal
At 11:03 PM 1/7/2002 +, Nicholas Clark wrote:
>If I've got this right, then this patch silences all warnings about unused
>variables, except for those from the ops files.
Applied. Thanks. (And sorry for the delay)
nder the impression that compilers warn about unused variables
based on what they see in the original source code.
(I think that gcc can't warn on them at -O0, as it needs the trace flow
analysis that the optimiser turns on to detect unused variables)
I don't think that that warn
On Mon, Jan 07, 2002 at 11:03:05PM +, Nicholas Clark wrote:
> --- include/parrot/parrot.h~ Sat Dec 15 14:21:03 2001
> +++ include/parrot/parrot.h Mon Jan 7 21:56:40 2002
> @@ -68,6 +68,11 @@
> typedef void* BIGINT;
> typedef void* BIGFLOAT;
>
> +/* define a macro to acknowledge an unus
If I've got this right, then this patch silences all warnings about unused
variables, except for those from the ops files.
This may not be the preferred way to do it, but it does flag where all the
unused parameters currently are.
Nicholas Clark
--- include/parrot/parrot.h~Sat Dec 15
