Hi,
Because I was two kinds of naughty when first creating my project, I've
created (outside CPAN) a set of modules in the IPAddress::Simple namespace.
The current incarnation is here:
http://code.google.com/p/perl-ipaddress-simple/source/browse/
The intent is to be a "better" Net::IPAddress, providing IPv4 and IPv6
support for individual addresses, address ranges, and collections of
ranges, with support for a variety of input and output formats. I didn't
want to hack on Net::IPAddress itself, for fear of breaking any existing
users of that module, which I imagine would be something of a catastrophe.
Before I put it on CPAN, there are some obvious deficiencies:
* Needs more test
* Needs more documentation
* Needs a new name
I hope to be able to handle the test scripts and documentation myself,
though if anyone's got any questions I can answer in the POD, or obvious
edge cases I've blatantly missed in the tests, or whatever, I'll happily
accept them.
Where the real problem comes is in the naming of the module. Talking to
the local Perl Mongers, it seems that Net::IPAddress::Util is their
preferred choice, giving the module names Net::IPAddress::Util,
Net::IPAddress::Util::Range, Net::IPAddress::Util::Collection, and
Net::IPAddress::Collection::Tie for single addresses, ranges of addresses,
collections of (ranges of) addresses, and super-secret under-the-covers
stuff, respectively.
Before I start renaming everything, I hoped you guys would have some
insights, or at least a yea/nay on that namespace choice.
So: any comments, questions, or suggestions?
Thanks,
--
Paul Bennett
