Linux worldls-302.fr.planethoster.net 4.18.0-553.8.1.lve.el7h.x86_64 #1 SMP Thu Jul 4 15:19:33 UTC 2024 x86_64
LiteSpeed
Server IP : 10.185.0.203 & Your IP : 216.73.216.32
Domains :
Cant Read [ /etc/named.conf ]
User : gerathty
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
usr /
local /
share /
perl5 /
Test /
use /
Delete
Unzip
Name
Size
Permission
Date
Action
ok.pm
1.33
KB
-r--r--r--
2019-02-06 04:55
Save
Rename
package Test::use::ok; use 5.005; our $VERSION = '1.302162'; __END__ =head1 NAME Test::use::ok - Alternative to Test::More::use_ok =head1 SYNOPSIS use ok 'Some::Module'; =head1 DESCRIPTION According to the B<Test::More> documentation, it is recommended to run C<use_ok()> inside a C<BEGIN> block, so functions are exported at compile-time and prototypes are properly honored. That is, instead of writing this: use_ok( 'Some::Module' ); use_ok( 'Other::Module' ); One should write this: BEGIN { use_ok( 'Some::Module' ); } BEGIN { use_ok( 'Other::Module' ); } However, people often either forget to add C<BEGIN>, or mistakenly group C<use_ok> with other tests in a single C<BEGIN> block, which can create subtle differences in execution order. With this module, simply change all C<use_ok> in test scripts to C<use ok>, and they will be executed at C<BEGIN> time. The explicit space after C<use> makes it clear that this is a single compile-time action. =head1 SEE ALSO L<Test::More> =head1 MAINTAINER =over 4 =item Chad Granum E<lt>exodist@cpan.orgE<gt> =back =encoding utf8 =head1 CC0 1.0 Universal To the extent possible under law, 唐鳳 has waived all copyright and related or neighboring rights to L<Test-use-ok>. This work is published from Taiwan. L<http://creativecommons.org/publicdomain/zero/1.0> =cut