Bil Kleb wrote:
> Is there a clear way to avoid this warning, or otherwise
> cir***vent it? (I still want to this warning for otherwise
> legitmate set-but-never-used cruft.)
Writing the variable silences the warning, so what about
writing to /dev/null or a scratch file? For example,
open(666,file='/dev/null') or open(666,status='scratch')
[..]
read(8) ignore
write(666,*) ignore ! to avoid 'set not used' warning
If the open was buried early on, this might not be too bad?
Regards,
--
Bil Kleb


|