Re: do, local and a qualified identifier?

I'm guessing someone might have "syntax-checked" the file with perl -c filename, and added the local as a way (not a good way, though) to suppress the "Name "Foo::bar" used only once: possible typo at foo.pl line 3." warning. (The warning isn't given when the file is invoked via do $filename because a file used that way is likely to use variables set elsewhere and set variables used elsewhere.)

Comment on Re: do, local and a qualified identifier? Download Code

Replies are listed 'Best First'.
Re^2: do, local and a qualified identifier? by Aristotle (Chancellor) on Oct 09, 2005 at 16:50 UTC
The only time my comments will contain anything close to swearing is next to a `no warnings 'once';` line at the top of my code, which is occasionally followed by `# sod off`. That warning is the single most useless thing ever – it has never ever caught a single mistake of mine but has inconvenienced me plenty. It might be useful for coding in the absence of the `vars` stricture (maybe?), but that’s the one stricture I always use. (I suppose you can tell it annoys me…) Makeshifts last the longest.	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: do, local and a qualified identifier?
by Aristotle (Chancellor) on Oct 09, 2005 at 16:50 UTC

The only time my comments will contain anything close to swearing is next to a no warnings 'once'; line at the top of my code, which is occasionally followed by # sod off. That warning is the single most useless thing ever – it has never ever caught a single mistake of mine but has inconvenienced me plenty.

It might be useful for coding in the absence of the vars stricture (maybe?), but that’s the one stricture I always use.

(I suppose you can tell it annoys me…)

Makeshifts last the longest.

[reply]
[d/l]