use Perl

• Some issues (Score:2, Informative)

  by Juerd (1796)

  Some issues:
  
  * The modules have no abstract (In NAME, one usually puts "Module::Name - Module that does something)
  * Prototypes are used for methods. That's useless, since they're ignored for runtime thingies. Besides that, have a look at Far More Than Everything You've Ever Wanted to Know about Prototypes in Perl.
  * POD is =cut and then immediately continued...
  * Some POD is broken otherwise (if you use multiple angle brackets, you must also use whitespace!)
  
  And probably more...
  • Re:Some issues (Score:2)

    by jonasbn (1153) <reversethis-{gro.napc} {ta} {nbsanoj}> on 2003.05.11 1:54 (#19996) Homepage Journal

    Thanks!
    
    I will correct these issues ASAP.
    
    I know that the prototypes aren't any good during run-time, but I use them when developing. They work quite well when refactoring code, that is why I tend to keep them around.
    
    Again - thanks for you feedback...

    Reply to This

    Parent

    • Re:Some issues (Score:3, Informative)

      by Dom2 (2981)

      Hmmm, I don't think you understand prototypes then... Have a look at the referenced article [perl.com].

      In short, prototypes are evil. Don't use them unless you have no other choice (see: Error.pm [cpan.org]).

      -Dom
      • Re:Some issues (Score:2)

        by jonasbn (1153)

        Two things jump out of the the article after a quick-read:

        1. From the 'Great Expectations [perl.com]' section: "Nearly any programmer you encounter will, when asked what function prototypes are for, report the standard text-book answer that function prototypes are mainly used to catch usage errors at compile time in functions called with an unexpected type or number of parameters. This is what programmers are expecting of prototypes, and what Perl does not give them. In some ways, it can't."
        2. From the Summary [perl.com]: "This do