Matt,
I gave some thought about your suggestion. While agreeing with you
that putting more modules under an "unsanctioned" name space might
give people a false impression of legitimacy and cause you guys
further grief, I'm not entirely comfortable with using my CPAN ID, for
the hubris factor we ha
Matt,
Thank you for taking your time and explain further. I now can gather a
couple things.
1. Util is deemed strongly undesirable as a top level namespace.
2. People -do- contribute under Util, but never have registered their
modules because Util is not sanctioned, and/or because they never want
On Mon, Jan 24, 2011 at 06:10:07PM -0800, Kan Liu wrote:
> On Mon, Jan 24, 2011 at 5:04 PM, Matt S Trout wrote:
> > All of these modules seem like they could have sensible names.
> >
>
> My sincere apologies that my naming scheme assaulted your sensibility.
> I've tried to correct them after Bria
All of these modules seem like they could have sensible names.
If you want to dump them into a top level namespace, might I suggest
KAN:: please? Util:: is meaningless and I really don't want people to
see that as a precedent.
Please, *please* stop uploading into Util:: and let's talk about *good
The following module was proposed for inclusion in the Module List:
modid: Util::AsyncIO::RW
DSLIP: MdpOp
description: async IO read/write reliable on EAGAIN
userid: KAN (刘刊)
chapterid: 23 (Miscellaneous_Modules)
communities:
Mailinglist/Chatrooms
similar:
