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.
  • Wouldn't it be great if existing modules could be modified by some kind of standardized plug-in architecture, so that the original module could be used without the plug-in or, at the user's option, could be used with a plug-in that would contain the desired enhancement/modification/perceived bugfix? I guess that would prevent forking, in a sense.

    Caution: I barely know what I'm talking about :-)

  • The problem as I see it (which is subjective), is that those patches exist. We do not expect Tony to write them for use from scratch. But it looks to me, that he just plainly refused to even take a look at those patches that were submitted.

    Of course that'll irk people up, especially those who wrote and submitted the patches, proud of their work, and being treated like some talentless freshman junior programmer.
    • Actually applying patches to a large project like CDBI is still nontrivial, especially if they are based on older code than under development.

      Also I haven't seen Tony dismiss any out of hand, he just has higher expectations than most when it comes to patches and fixes - not just good code, but tests and a good reason to change stuff.

      Patches have got in, and he has been working on making the infrastructure of the code easier and more consistent to extend.

      Unfortunately a large number of patches that most peop
      --

      @JAPH = qw(Hacker Perl Another Just);
      print reverse @JAPH;
  • "What is the correct relationship between a CPAN module author and the module users?"

    Easy. While we the amount of maintenance and support provided (or lack thereof) is debatable, how about starting with something like:

    • The module author should not threaten to sue users over stupid things.