4 ms·
On the one hand, this is really cool. On the other, I'm always sad to see projects like this which seem to follow Perl 4 Best Practices type design. By this, I
by autarch 12y ago
On the one hand, this is really cool. On the other, I'm always sad to see projects like this which seem to follow Perl 4 Best Practices type design. By this, I mean ...
* No strict or warnings
* Calling subs with "&foo" syntax
* Globals, globals everywhere
It's cool that Perl just lets you whip things up with so little ceremony, but it's always nice when people write nice code, in any language.
- peteretep 12y agoI always love it when someone does something awesome in Perl, but always a little scared to see the code :-( A sad thing here is that the code looks like it mostly would run under strict and warnings, and it'd be pretty easy to simplify the sub definitions at the start
- zzzcpan 12y agoStrict is not that big of a deal and can be easily enabled later. Seriously, those issues with the code are really tiny and very unimportant, especially for this project. But I would definitely choose this kind of code over anything with Moo* for example. It's sad that people don't know or forget what makes a code easier to understand and how important it is.