I'm sick of continually seeing Date/Time modules posted to CPAN that are yet more crazy ways of doing things. The latest (Time::Local::Extended) is basically a hack on Time::Local that subtracts 60 years if it looks like the date in question may be over 2038!

The other thing I'm sick of (the above module really made my blood boil!) is modules that do more than one thing! The above module can also format and parse such dates in a mySQL friendly manner!

I really wish there was some method of quality control on CPAN.

I guess what I'd really like is an 'Experts Exchange' type thing where experts in particular fields are able to include or exclude a module in CPAN's main archive (lets call this non-main archive the 'bleeding' archive) So:


CPAN> install Time::Local::Extended


The package 'Time::Local::Extended' has not been included in the main CPAN archive. It is recommended that you read www.cpan.org/bleeding/Time-Local-Extended-0.04 before you install this module with 'install bleeding Time::Local::Extended'.

This may be because the package is new to CPAN and hasn't been checked yet, or that there is some concern regarding its use.

CPAN>


While I'm at it, I'd also like module maintainers to authorise any modules posted below theirs. Thus if I've uploaded Foo::Bar and you want to upload Foo::Bar::Baz, you'd need my permission. If Dave has uploaded DateTime and you want to upload DateTime::Event::Easter you need his permission (or permission from the maintainer of DateTime::Event (if that exists))


</rant>

Cheers!
Rick Measham



Senior Developer
PrintSupply - Print Procurement & Supply Management
18 Greenaway Street VIC 3105
Tel: (03) 9850 3255
Fx: (03) 9850 3277
http://www.printsupply.com.au/



Reply via email to