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.

modules@perl.org 4 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I am on said list, and took no offense.

    There could be a section/topic on use Perl for people to ask questions about modules, too.

    • Re:modules@ (Score:1)

      by godoy (2167) on 2002.01.09 21:52 (#2975) Homepage Journal
      Although it seems interesting, I don't think it's good doing that.

      I read that list through the newsserver, not the mailing list, and I think that we should advertise it instead of finding alternatives to it.

      We already have News and mail to post / read there, why forking (or creating a third alternative) on use.perl?
      --
      -- Godoy.
      • modules@perl.org is not good for getting responsive discussions about module purposes and names. It is for getting something resembling formal approval (or disapproval). However, if you want to really talk something out, and no one on modules@perl.org wants to respond for whatever reason, what do you do?
        • The same thing you do on the other mailing lists? What happens if nobody answers me on AxKit ML? Or at mod_perl ML? I'm against duplicating things. Maybe bringing up the topic here might be a good idea on rare occasions.

          Really, having something here sporadically is OK, but making it permanent? I don't know.

          BTW, I think I should have written that at the submitted story, not here on Matts' diary. :o) Sorry. I just had no time to read the things there...
          --
          -- Godoy.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.