Oooh...

Matts on 2003-04-17T09:52:50

I bet a few people are gonna be hopping mad about this ;-)


No Doubt!

LTjake on 2003-04-17T11:24:34

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!

Re:No Doubt!

koschei on 2003-04-17T13:34:54

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. =)

Re:No Doubt!

LTjake on 2003-04-17T14:49:27

Ah, damn you. =D

This should still be read more often...

Re:No Doubt!

koschei on 2003-04-18T03:59:51

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 =)

Perl 4

malte on 2003-04-17T12:23:26

Oh, this has been on CPAN for ages. You can tell, because it uses Perl 4 style function calls all over the place.

&date_get();

:)

Protect thy namespace!

johanvdb on 2003-04-17T13:13:59

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 ...

Johan