use Perl

• please, no (Score:1)

  by perrin (4270)

  Sorry Ovid, but this is an abomination. It kind of sums up many of the problems with Perl culture: obsession with syntax over utility, willful use of obscure features like using the import list for other things, and a desire to make everything REALLY short. Give the module a normal name, call the alias method like a normal method, and give intermediate perl programmers a chance in hell of understanding your code. Otherwise, it belongs in Acme::.
  • Re:please, no (Score:2)

    by ziggy (25)

    I was going to post a flame about how the whole point of programming language design is to obsess over syntax in the name of achieving greater utility. That's what gave us idioms like 'open or die' and foreach loops over hand-compiling tail recursive forms.

    But I see that your clarification, and yes, the abuse of the import list is quite horrid.

    Perl is a dynamic language. There's no reason why the magic fiddling must happen at compile time, nor is there any reason why it the aliasing must use a use sta
    • Re:please, no (Score:1)

      by perrin (4270) on 2005.01.05 13:24 (#37257) Journal

      I like that API much better. My beef with the original API is that it uses pragma-like names and a non-obvious use of import (which is unfortunately catching on because of Test::More), and all for the sake of syntax rather than added functionality. To me, it looks like a disregard for the larger effects on the community, i.e. if everyone did crazy stuff like this to get a particular syntax for their modules, CPAN would be a total disaster. I have also seen this kind of thing get people into trouble, as in the dangerous try/catch syntax of the otherwise useful Error.pm module.

      The need to learn lots of little syntaxes is the kind of thing that people complain about when they are trying to pick up Perl after knowing another language. I think it should be avoided when possible.

      Reply to This

      Parent