Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I'm looking forward to you in-depth review of the actual codebases and not just syntextual suger, as you are probably aware some of the some competitors has re-implemented a lot of existing mature codebases on CPAN, such as RFC: 2109, 2388, 2616, 4627, etc.

    And simple thing like I/O and syscalls (logging error reporting) etc...

    -- chansen

    • See comment below please.
    • I won't be reviewing their code unless, for some reason, some failure takes me chasing down into it in the debugger.

      However, I may end up commenting on their APIs and naming if it sticks out as unusual

    • A code review may not be as useful. What users almost always want to know is:

      • Does it do what I need?
      • Is it easy to learn?
      • Can I trust it? (less so on this one, unless they'll be using it for the long haul)

      One issue with code reviews is that reviews are terribly subjective [perlmonks.org]. If I have a different take on how to approach a problem, I might very well ding someone on a review because I didn't understand/appreciate their code.