Dave, Can you explain what functionality wasn't available in NetAddr::IP that you needed? (I use that at work for IP and subnet handling.)
Can you talk a little bit about the rough edges you needed to smooth over? Given you were already writing a bunch of wrappers around NetAddr::IP, why did you decide to use Net::IP for ip_inttobin and ip_bintoip? (ip_inttobin is basically just $NAIP->bigint->as_bin with some extra formatting.) Why would I want to stop using NetAddr::IP and switch to these modules instead? Are there any reasons that I wouldn't want to switch? (I'm curious about these because I too wrote some wrappers around NetAddr::IP. We use ours for fun stuff like generating large DHCP configuration files from network information stored in a database. If I ever get around to genericizing it, I'll be sure to release on CPAN because someone else might also find it useful.) Thanks for your time, Matt Matt On Mon, Nov 12, 2012 at 4:53 PM, Dave Rolsky <auta...@urth.org> wrote: > We created a few new modules for working with IP addresses and subnets at > MaxMind which we'd like to release. Internally we've been calling them > MM::Net::IPAddress and MM::Net::Subnet but obviously those names won't work > for CPAN. > > I've posted a PrePAN review request to discuss this further - > http://prepan.org/module/**429En4oFfc<http://prepan.org/module/429En4oFfc> > > Please discuss there if possible, but on list is fine too. > > > Thanks, > > -dave > > /*============================**==============================**== > http://VegGuide.org http://blog.urth.org > Your guide to all that's veg House Absolute(ly Pointless) > ==============================**==============================***/ >
