Re^2: Strict isn't strict enough

Replies are listed 'Best First'.
Re^3: Strict isn't strict enough by JavaFan (Canon) on Dec 31, 2011 at 17:20 UTC
ANYTHING can be typoed, and then cut-and-pasted. If your coding style is to randomly hit the keyboard, and then ask perl whether you did a good job, don't expect `use strict;` to be a silver bullet. Perhaps you should replace `/usr/bin/perl` with `#!/usr/bin/sh echo "Possible typo detected at line 1. Please fix." exit 1` [download] BTW, what should perl do if you did `my $hwatever` and then cut-and-pasted the `$hwatever`?	[reply] [d/l] [select]
Re^4: Strict isn't strict enough by davies (Monsignor) on Dec 31, 2011 at 17:31 UTC
what should perl do if you did my $hwatever and then cut-and-pasted the $hwatever? Give a compile time error when I use `$whatever`. Obviously it isn't a problem if the same typo is used throughout, but if a variable can be used in two places then there is scope for typos that I expected `strict` to catch before I read the docs. I still want to catch it if I can. Regards, John Davies	[reply] [d/l] [select]
Re^5: Strict isn't strict enough by JavaFan (Canon) on Jan 01, 2012 at 01:19 UTC
So, what should happen at: `package Foo; declare $slave::whatever; # Inventing a keyword to declare fully qual +ified names. $slave::whatever = 1; __END__ package Bar; declare $slave::hwatever; print $slave::hwatever; __END__` [download] Typo, or intentional?	[reply] [d/l]
Re^6: Strict isn't strict enough by davies (Monsignor) on Jan 01, 2012 at 11:39 UTC
Re^7: Strict isn't strict enough by BrowserUk (Patriarch) on Jan 01, 2012 at 12:12 UTC