in reply to Re^3: Back to the __future__
in thread Back to the __future__

what's is the purpose of saying "I need Perl 5.xx or higher"?

That way we can specify a minimum release.

I suggested that particular syntax because it uses existing syntax rather than inventing new, so versions up to and including 5.14 don't barf.

I appreciate that the meaning of the use will change to mean emulate a particular release, I'm querying whether that will be always feasible. If a feature needs to be changed, then being able to support both new and old could make the code even more complex, and might not always be possible every time. I think Jesse said as much in his talk, at least that was the impression I got.

Replies are listed 'Best First'.
Re^5: Back to the __future__
by JavaFan (Canon) on Aug 21, 2011 at 12:39 UTC
    That way we can specify a minimum release.
    But why? Keeping the ability to say "I want version X or anything newer" means that there's absolutely no benefit in going with Jesse's proposal. And then we may as well keep what we have. The entire point of the exercise is the ability to change/refine the meaning of existing syntax without breaking existing code.

    Putting the "old" meaning of use back in using a different construct means we're back to square one.