finding shadowed globals when strict compilation is on

[Dr. Hawkins]

I have a recurring problem that a variable name was apparently called
global *somewhere* in my multitude of scripts (hundreds?).

I then declare it local elsewhere, and strict compilation throws a
tizzy, blocking everything, even though it isn't available in the
local scope.

Is there *any* way to find out the offending other variable when
"local name shadows" ??

-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462