Acme-What
view release on metacpan or search on metacpan
what is happening?
what is the problem?
Acme::What is lexically scoped, so you can define different handling for
it in different parts of your code. You can even use:
no Acme::What;
to disable Acme::What for a scope. (The `what` keyword is still parsed
within the scope, but when the line is executed, it throws a catchable
error.)
WHY?
It's in the Acme namespace. There is no why.
HOW?
Acme::What uses Devel::Declare to work its magic.
WHITHER?
Devel::Declare, Acme::UseStrict.
lib/Acme/What.pm view on Meta::CPAN
what is happening?
what is the problem?
Acme::What is lexically scoped, so you can define different handling for
it in different parts of your code. You can even use:
no Acme::What;
to disable Acme::What for a scope. (The C<what> keyword is still parsed
within the scope, but when the line is executed, it throws a catchable
error.)
=head1 WHY?
It's in the Acme namespace. There is no why.
=head1 HOW?
Acme::What uses L<Devel::Declare> to work its magic.
t/01basic.t view on Meta::CPAN
what 2; 0;
what 3;
}
{
use Acme::What 'passit';
sub passit { ok @_ }
my $i_am_going_to_give_you = what 4
throws_ok {
no Acme::What;
what now?
} qr{Acme::What};
}
( run in 0.369 second using v1.01-cache-2.11-cpan-496ff517765 )