>Tom Christiansen wrote: >> >> >Anything else? Any opinion on whether eval "" should do what it does >> >now, and be invisible for the purposes of this analysis; or if it should >> >be assumed to instead both use and initialize all visible variables? The >> >former produces more spurious warnings, the latter misses many errors. >> >> You have to assume eval STRING can do anything. >> >> --tom >"have to"? Perl5 doesn't. You mean "perl". >% perl -we '$x = 3; $v = "x"; eval "\$$v++"' >Name "main::x" used only once: possible typo at -e line 1. Non sequitur. And no, I don't have time.
- Re: RFC 12 (v2) variable usage warnings Tom Christiansen
- Re: RFC 12 (v2) variable usage warnings Steve Fink
- Re: RFC 12 (v2) variable usage warnings Bart Lateur
- Re: RFC 12 (v2) variable usage warnings Dave Storrs
- Re: RFC 12 (v2) variable usage warnings Eric Roode
- Re: RFC 12 (v2) variable usage warnings Steve Fink
- Re: RFC 12 (v2) variable usage warnings Tom Christiansen
- Re: RFC 12 (v2) variable usage warnings Steve Fink
- Re: RFC 12 (v2) variable usage warnings Tom Christiansen
- Re: RFC 12 (v2) variable usage warn... Steve Fink
- Re: RFC 12 (v2) variable usage ... Tom Christiansen
- Re: RFC 12 (v2) variable usage ... Steve Fink
- Re: RFC 12 (v2) variable usage ... Tom Christiansen
- Re: RFC 12 (v2) variable usage ... Daniel Chetlin
- Re: RFC 12 (v2) variable usage ... Steve Fink
- Re: RFC 12 (v2) variable usage warnings Dave Storrs
- Re: RFC 12 (v2) variable usage warnings Steve Fink
- Re: RFC 12 (v2) variable usage warnings Eric Roode
- Re: RFC 12 (v2) variable usage warnings Steve Fink