But increased readability increases maintainability. IMHO the equivalence of
sub fexists (-f $_[0] ? $_[0] : undef); my $file = fexists ($p) // fexists ("$p.exe") // fexists ("$p.sh") // +…;
would involve lexical copies and a huge chain of defined ($x) ternaries.
So yes, many new features were doable in older versions, but they were ugly and error-prone.
I myself do NOT like OO programming. I need to understand how perl does it when dealing with modules that have no non-OO alternative, like DBI and Tk, but I still prefer to program non-OO myself. Moose however makes the threshold to actually *use* OO in perl in a way that does not constantly irritate me a lot lower (if it does take away the threshold at all). That on itself is worth considering, as that also makes the language more open to newcommers. OO-programmers get a head-start with Moose over the available OO techniques that the CORE has available.
In reply to Re^5: Stop suggesting to upgrade perl
by Tux
in thread Stop suggesting to upgrade perl
by vsespb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |