Re:Why Perl Didn't Win
by Joeri on Monday June 09, 2014 @05:51AM
(#7867664)
Sane defaults are a cornerstone of good language and framework design because for better or worse people don't read the manual before they start using something. If a compiler doesn't do the right thing by default (throwing errors on problems a new user is likely to cause), it's a bad compiler.
[ Parent
| on HN ]
Re:Why Perl Didn't Win
by BugBrother on Monday June 09, 2014 @06:20AM
(#7867728)
What sane defaults are will change over the years.
Perl kept amazing backwards compatibility by adding extra statements to modify how it worked. So "use strict;", "use warnings;" and "use <other_newer_perl_features>;".
Both new code -- using the best OO system of the scripting languages, extendable syntax, etc, etc -- will run at the same time as most of the old and crufty stuff from before testing took over after the Millennium.
Lines that can affect the global behavior of the program are a mixed blessing.
Re:Why Perl Didn't Win
by BugBrother on Monday June 09, 2014 @11:06AM
(#7868781)
It would have been bad, if the design had been stupid enough to not make declarations file/package based... :-)