Re^2: Doubt in Eval

Replies are listed 'Best First'.
Re^3: Doubt in Eval by zwon (Abbot) on Feb 17, 2012 at 03:38 UTC
Common sense is to use strict and warnings.	[reply]
Re^4: Doubt in Eval by Anonymous Monk on Feb 17, 2012 at 03:45 UTC
`perldoc common::sense NAME common::sense - save a tree AND a kitten, use common::sense! SYNOPSIS use common::sense; # supposed to be the same, with much lower memory usage, as: # # use utf8; # use strict qw(vars subs); # use feature qw(say state switch); # no warnings; # use warnings qw(FATAL closed threads internal debugging pack # portable prototype inplace io pipe unpack mallo +c # deprecated glob digit printf layer # reserved taint closure semicolon); # no warnings qw(exec newline unopened);` [download]	[reply] [d/l]
Re^5: Doubt in Eval by zwon (Abbot) on Feb 17, 2012 at 07:08 UTC
I know what common::sense is, but I argue that one should use common sense (without double colon)	[reply]
Re^6: Doubt in Eval by tobyink (Canon) on Feb 17, 2012 at 13:49 UTC
Re^3: Doubt in Eval by Anonymous Monk on Feb 17, 2012 at 13:55 UTC
$ corelist strict warnings Common::Sense strict was first released with perl 5 warnings was first released with perl v5.6.0 Common::Sense was not in CORE (or so I think) $ [download] Requiring the installation of a module that does little but save typing? Virtuous Laziness is not about pushing work off onto others. Additionally strict refs is more useful than not & can be easily disabled in the few scopes that it actually gets in the way. I agree w/ zwon. Common Sense is better w/o the double colon.	[reply] [d/l]