Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • I couldn't help but ask myself, what was he thinking? It's not like he doesn't know about datetime [] - he's on the datetime mailing list... (see this message []).

    Give a hoot, don't pollute!

    • Actually, he didn't know about the DT project.

      I emailed him after he uploaded Date, Time and DateTime, informing him of the project and recommending he schedule his modules for deletion.

      That message you reference is after that. =)
        ---ict / Spoon
      • Ah, damn you. =D

        This [] should still be read more often...

        • Absolutely! Everyone needs to read more! Perhaps such things need to be highlighted further? Mind you, I barely remember the PAUSE web interface for uploads; I've been using the cpan-upload script for quite some time =)

          I pointed out perlnewmod and such to him as well =)
            ---ict / Spoon
  • Oh, this has been on CPAN for ages. You can tell, because it uses Perl 4 style function calls all over the place.



  • I wonder ... can't we lock some name spaces on CPAN, so that not everybody can update reserved module names?

    I know it is a bit against the free-for-all culture that has been been the driving factor behind CPAN. but, be real, we should take care to make the pollution of CPAN less obvious ;-)

    I'm not talking about rigorous measures here, we need to make sure CPAN stays open and free for non critical namespaces. But we should also have a more restricted access policy to some Perl core name spaces. Maybe modelled after the way a registered name space is granted for the moment - by using the mailing list ...

    Just my 5€ cents ...