You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A problem here is that perl can identify that something is a version by its literal form in the source code. That is:
use Some::Module 1.2;
use Some::Other "1.2";
use Some::Again (1.2);
In the first case, it is a version check for 1.2. In the second and third cases, an import request. use_ok can't determine this, because by the time it gets its @_, it's a variable that could be either.
I do not believe this can be made to do what you want.
- RC1
- Merge Test2 into the Test-Simple dist
- Remove experimental status
- Update copyright dates
- Better error messages when using Carp in Hashbase init()
- Document 2 methods on Events
- Fix Test2 #17 (typo fix in docs)
- Report version mismatches between Test::Builder and Test2
- Update transition docs
- Breakage library and warnings
I have problem with version in use_ok:
use_ok (module, 1.0.0);
use_ok (module, v1.0.0);
after quick look in source codes (Test::More, version 0.94) following fix
comes to my mind (change line 816 with it):
$imports[0] = join '.', unpack 'U*', $imports[0]
if 'VSTRING' eq ref \ $imports[0];
if( @imports == 1 and$imports[0] =~ /^\d+(?:.\d+)*$ / ) {
Could you please show the output you got and what you expected? I think I know what
you're talking about, but I'd like to be sure.
for given examples i expect that use_ok use version check, same like perl do.
now, Test::More use import with arguments.
See also http://www.perlmonks.org/?node_id=809447
The text was updated successfully, but these errors were encountered: