Skip to content

Commit

Permalink
[S11] added 'v' to version numbers within :ver()
Browse files Browse the repository at this point in the history
When the version numbers are within :ver<>, the 'v' can be omitted. But in
:ver() they shouldn't be, because they'd be parsed as decimal numbers.

git-svn-id: http://svn.pugscode.org/pugs@26304 c213334d-75ef-0310-aa23-eaa082d1ae64
  • Loading branch information
masak committed Apr 20, 2009
1 parent 9ef5541 commit 2fc7c56
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions S11-modules.pod
Expand Up @@ -329,9 +329,9 @@ Saying C<1.2.1> specifies an I<exact> match on that part of the
version number, not a minimum match. To match more than one version,
put a range operator as a selector in parens:

use Dog:ver(1.2.1..1.2.3);
use Dog:ver(1.2.1..^1.3);
use Dog:ver(1.2.1..*);
use Dog:ver(v1.2.1..v1.2.3);
use Dog:ver(v1.2.1..^v1.3);
use Dog:ver(v1.2.1..*);

When specifying the version of your own module, C<1.2> is equivalent
to C<1.2.0>, C<1.2.0.0>, and so on. However C<use> searches for
Expand Down Expand Up @@ -361,7 +361,7 @@ to guarantee that you get the unembraced Perl. C<:-)>

For wildcards any valid smartmatch selector works:

use Dog:ver(1.2.1 | 1.3.4):auth(/:i jrandom/);
use Dog:ver(v1.2.1 | v1.3.4):auth(/:i jrandom/);
use Dog:ver(Any):auth({ .substr(0,5) eq 'cpan:'})

In any event, however you select the module, its full name is
Expand Down

0 comments on commit 2fc7c56

Please sign in to comment.