Re^5: local our $var; What does it do?

Indeed :)

But it does beg the question; why when you have to explicitly enable a feature, do you have to also explicitly disable the warnings that are meaningless when you've explicitly requested the feature?

It's like when I'm using hex constants in a 64-bit build of perl and I have to explicitly disable these asinine warnings:

Hexadecimal number > 0xffffffff non-portable at C:\test\mandlebrot\dou
+bleDouble.pl line 57.
Hexadecimal number > 0xffffffff non-portable at C:\test\mandlebrot\dou
+bleDouble.pl line 58.
Hexadecimal number > 0xffffffff non-portable at C:\test\mandlebrot\dou
+bleDouble.pl line 59.
[download]

There is some asinine pedant in p5p adding this shit. I guess I could look up who; but then I'd feel the need to say something personal.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority". I'm with torvalds on this

In the absence of evidence, opinion is indistinguishable from prejudice. Agile (and TDD) debunked

Comment on Re^5: local our $var; What does it do? Download Code

Replies are listed 'Best First'.
Re^6: local our $var; What does it do? by ikegami (Patriarch) on Jun 18, 2015 at 17:15 UTC
It was probably more useful back in the day when there were few 64-bit machines. It's time this warning got abolished. They're talking about creating warnings not enabled by `use warnings;` (as opposed to `use warnings 'all';`). I disagree with that, but if they through with it, the warning could be demoted instead of abolished.	[reply] [d/l] [select]