Cisco Cisco ASA 5555-X Adaptive Security Appliance 许可信息

"Carp.pm" module - doesn't help).

 

The purpose and advantage of this is that a "clan" of

modules can work together (and call each other) and throw

exceptions at various depths down the calling hierarchy

and still appear as a monolithic block (as though they

were a single module) from the perspective of the caller.

 

In case you just want to ward off all error messages from

the module in which you "use Carp::Clan", i.e., if you

want to make all error messages or warnings to appear to

originate from where your module was called (this is what

you usually used to "use Carp;" for ;-) ), instead of

in your module itself (which is what you can do with a

"die" or "warn" anyway), you do not need to provide a

pattern, the module will automatically provide the correct

one for you.

 

I.e., just "use Carp::Clan;" without any arguments and

call "carp" or "croak" as appropriate, and they will

automatically defend your module against all blames!

 

In other words, a pattern is only necessary if you want to

make several modules (more than one) work together and

appear as though they were only one.

 

 

Contact Authors:

----------------

 

Joshua ben Jore <jjore@cpan.org>

http://perlmonks.org/?node=diotalevi

 

Steffen Beyer <stbey@cpan.org>

http://www.engelschall.com/u/sb/download/

 

 

 

COPYRIGHT

   Copyright (C) 2001-2005 Sherzod Ruzmetov <sherzodr@cpan.org>. All rights reserved.

   This library is free software. You can modify and or distribute it under the same

   terms as Perl itself.