in reply to Re^5: Why version strings?
in thread Why version strings?

That delays the version check to run-time,

You know how to execute code at compile-time.

That would be an argument against the entire use 5.XXX; syntax;

There may be the premise for an argument, but there's no an argument. Could you actually state this argument? I can't guess what it could be.

it also assumes there's only one Perl version on the system

No it doesn't because each has its own lib directory.

Before you mention PERL5LIB or local::lib, consider that they already break when you use them with more than one version of Perl. (PERL5LIB breaks if the directory was built using the suggested INSTALL_BASE, and local::lib breaks because it uses INSTALL_BASE.)

Not to mention many scripts don't come with an installation script.

So? Are you trying to say that no scripts should come with an installation script?

Replies are listed 'Best First'.
Re^7: Why version strings?
by JavaFan (Canon) on Mar 29, 2011 at 21:24 UTC
    Can we just conclude that you don't know the answer to my question:
    I don't know whether there's a (single-line) syntax that at compile time checks for 5.10, but which doesn't enable features.
    either?
[reply]

      Is that a weird way of letting me know that «BEGIN { require 5.010; }» is buggy in 5.10 and 5.12, but fixed in 5.14? That leaves

      • BEGIN { die if $] < 5.010_000 }
      • use 5.010; no feature ":5.10";
      • { use 5.010; }
[reply]
[d/l]
[select]

      How about:

      BEGIN { die "Not new enough" if $] < 5.016; }
[reply]
[d/l]

In Section Seekers of Perl Wisdom