Re: request for change
Matt Lewis wrote:
>
> also the case of unused global constants that are part of a library,
(Minor correction: unused global constants, variables, and routines do not
generate warnings, for sound reason, nor in fact and to my dislike do unused
local routines, it is only unused local constants and variables that trigger such
messages.)
> I think it's better to require affirmative
> action from the programmer to turn off the warnings.
I agree, and would even support a ridiculously extreme method of *forcing* every
individual warning to be explicitly counteracted, eg:
without warning "parameter self in myhandler is not used"
procedure myhandler(integer self, integer msg...
whereby the without warning directive pushes entries onto a stack that are
filtered by and popped off by matching warning messages, and generate errors when
[any] eof is reached for any left unpopped.
Somehow doubt many would want to go that far though 
Fwiw, Edita does not need any "without warning" statements (though ppp.e has
one, I just killed one in pFinet.ew, and not counting arwen).
Regards,
Pete
|
Not Categorized, Please Help
|
|
