in reply to Re: Question about making modules.
in thread Question about making modules.

Put in a required minimum Perl version.

Gah. Please don't. Don't proclaim "This requires Perl version X" unless you actually know that it really does require it. And if you do go to the effort of figuring out that a particular version is required, then please be quite specific in describing why that particular version is required (at the least).

I'd much rather get an error that points right at the thing that isn't supported with my version of Perl than be told "The author of this module has decided to prevent this module from even attempting to run on your version of Perl but absolutely no insight as to why was provided." That's just rude or worse.

Update: It'd be nice if "use 5.006_001('open my $fh');" were supported so that when an author provides insight we don't have to go hunting for it.

- tye        

  • Comment on Re^2: Question about making modules. (perl ver)

Replies are listed 'Best First'.
Re^3: Question about making modules. (perl ver)
by dragonchild (Archbishop) on Jul 06, 2008 at 21:07 UTC
    I'm with you there. Being able to specify minimum feature requirements vs. minimum version is a much nicer solution, and not just for Perl versions.

    In the meantime, specifying a minimum Perl version is better than failing randomly after installation. To me, "use 5.006_000;" is important because of the number of times I've moved files from Pure-Perl modules around and hit random bugs.

    My criteria for good software:
    1. Does it work?
    2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
[reply]

In Section Seekers of Perl Wisdom