Re: Philosophy for when not to support older versions of perl


There's more than one way to do things
	PerlMonks

Re: Philosophy for when not to support older versions of perl

by VinsWorldcom (Prior)

on Mar 30, 2016 at 01:01 UTC ( [id://1159064]=note: print w/replies, xml )

Need Help??

in reply to Philosophy for when not to support older versions of perl

Just as an example, I do a lot of network programming and a few years back went through and added IPv6 support to my modules. IIRC, IPv6 routines (get*info(), inet_ntop/pton()) didn't show up in Socket.pm until around 5.14 and even later for IO::Socket::IP to be included in core. So I have extensive workarounds to "detect" if IPv6 is supported on the version of Perl and then spit a warning / error to upgrade, add Socket6, or whatever the fix would be.

I suppose I could have just bumped the required Perl version in my Makefile.PL, but the IPv4 portion of my modules worked fine and I felt adding IPv6 shouldn't discontinue use of a working IPv4 piece of code on older Perls.

Not sure if that helps or answers your question?

Comment on Re: Philosophy for when not to support older versions of perl

Replies are listed 'Best First'.
Re^2: Philosophy for when not to support older versions of perl by stevieb (Canon) on Mar 30, 2016 at 01:12 UTC
That's definitely a great example. I'm an Internet network engineer by trade (my tech trade that is, much of my time has been divested in IPv6 since the early adoption phase), and actively seek out network modules on CPAN looking for fixes that may need had. This situation is one where it was worth the time spent (imho).	[reply]

In Section Meditations

Domain Nodelet^?

www.com | www.net | www.org

Node Status^?

node history
Node Type: note [id://1159064]
help

Chatterbox^?

How do I use this? • Last hour • Other CB clients

Other Users^?

Others lurking in the Monastery: (3)

As of 2024-04-26 04:29 GMT

Sections^?

Information^?

Find Nodes^?

Leftovers^?

Today I Learned

Voting Booth^?

No recent polls found