Re^2: RFC: Tutorial: use strict; now what!?

Replies are listed 'Best First'.
Re^3: RFC: Tutorial: use strict; now what!? by Eliya (Vicar) on Feb 08, 2012 at 17:43 UTC
Lumping strict and warnings together is a mistake. I beg to disagree. Many times (not only here, but at my workplace, too) I've seen people hunting for bugs for way too long, simply because they thought "I don't need no stinking warnings". Had they had them enabled, they would have been pointed to the root cause of the problem more or less directly. And if you feel annoyed by the "use of uninitialized value"s (and you know what you're doing), it's no big deal to disable those specifically with `no warnings "uninitialized";` — at least that doesn't qualify as "a lot of work" in my opinion. I agree there are rare circumstances where you don't want them — for example, I've seen a few cases (very few actually) where leaving warnings enabled in production environments has led to more problems than it solved — but as a development tool, I'd always recommend `use warnings;`	[reply] [d/l] [select]
Re^4: RFC: Tutorial: use strict; now what!? by educated_foo (Vicar) on Feb 08, 2012 at 18:02 UTC
The solution is pretty simple: if your code isn't doing what you expect, run it with "`perl -w`". This may point to your error (along with a bunch of other non-errors); if it does, you can fix it and move on without having to contort your code to placate warnings.	[reply] [d/l]
Re^5: RFC: Tutorial: use strict; now what!? by chromatic (Archbishop) on Feb 08, 2012 at 18:58 UTC
This may point to your error (along with a bunch of other non-errors);... ... and a bunch of warnings in other places that aren't under your control. warnings has a lexical scope, while `-w` and `-W` affect the entire process.	[reply] [d/l] [select]
Re^6: RFC: Tutorial: use strict; now what!? by educated_foo (Vicar) on Feb 08, 2012 at 19:08 UTC
Re^7: RFC: Tutorial: use strict; now what!? by chromatic (Archbishop) on Feb 08, 2012 at 19:38 UTC
Some notes below your chosen depth have not been shown here
Re^5: RFC: Tutorial: use strict; now what!? by Eliya (Vicar) on Feb 08, 2012 at 18:21 UTC
Well, "`perl -w`" is "enabling warnings", too. I don't specifically care whether people use "`use warnings`", "`-w`" on the command line, or "`-w`" on the shebang line, as long as they do enable warnings when appropriate.	[reply] [d/l] [select]
A reply falls below the community's threshold of quality. You may see it by logging in.


laziness, impatience, and hubris
	PerlMonks