Can I just say
How cool perldoc.perl.org is? There. I've said it.
Hats off to all involved.
How cool perldoc.perl.org is? There. I've said it.
Hats off to all involved.
I've only known you for a few months defined-or but if you leave me know you'll take away the biggest part of me.
State vars, lexical $_, smart matching and switch statements are all wonderful as well.
A big thank-you to all you perl 5.1x contributors out there.
jared recently took considered - if mischievous - aim at the Modern Perl crusade:
http://curiousprogrammer.wordpress.com/2010/07/29/does-your-perl-suck-if-you-dont-use-moose
A recent post from chromatic was the inspiration:
http://www.modernperlbooks.com/mt/2010/07/a-checklist-for-writing-maintainable-perl.html
I'd go further.
No amount of automati…
There is empirical evidence that Perl is an inherently maintainable language. The Software Productivity Research group have published 2 comprehensive surveys of programmer productivity across different languages and problem domains. One was published in 1996, the other in 2006. The results in both are consistent - for overall perl productivity scores & when perl is compared against other popular languages.
Function points were used as the data collection method and the survey covered the whole dev lifecycle. The actual…
I like dispatch tables. Which means I use this kind of thing quite a bit:
$dispatch{$pieces_of_state}->(@args)
if exists $dispatch{$pieces_of_state};
Does that sub-routine call look ugly? I suspect it does. It would look nicer in javascript for sure:
dispatch[pieces_of_state](args)
vs
$dispatch{$pieces_of_state}->(@args)
But how much difference does the syntax really make? I understand the impulse to make perl look more like Haskell but I doubt very much that the extra noise from the sigils ma…