Right, well by extension you could not `use warnings` - because it essentially does the same by enabling :all, and instead you can use each different type of warning explicitly. You could do the same thing with strict too! Even CORE has to make some defaults: $[ defaults to 0.
Other than the extremely weak argument you present, the point I'd like to make is that there is a level of reasonableness to getting better defaults. That comes at the cost of "defaults" - choices being made by someone else that *might* not apply to you, but *may* very well be so crafted as to benefit you in every application.
In reply to Re^2: Writing a better Modern::Perl
by EvanCarroll
in thread Writing a better Modern::Perl
by EvanCarroll
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |