On Thu, 9 Jan 2014 16:49:21 +0000 Nicholas Clark <nick@ccl4.org> wrote: > By using Acme::Overide::INET (thanks xdg, this makes things a lot > easier)* I've found a couple of things that differ in behaviour from > IO::Socket::INET, and aren't documented as incompatibilities. > Reported as > > https://rt.cpan.org/Public/Bug/Display.html?id=91982 > https://rt.cpan.org/Public/Bug/Display.html?id=91989 > > In one case, we seem to be getting a silent constructor failure. Having looked at them, they both fall into the category of "existing code doing morally-dubious things with IO::Socket::INET that nevertheless managed to work there", which isn't going to work in a more general case. Hard to see what a sensible course of action is here. I'm not overly inclined towards making IO::Socket::IP do odd things just because ::INET did them, so they may have to be filed under the general banner of "don't do that". -- Paul "LeoNerd" Evans leonerd@leonerd.org.uk ICQ# 4135350 | Registered Linux# 179460 http://www.leonerd.org.uk/Thread Previous | Thread Next