comment on

Yeah, you're right, looks like I got them the wrong way around . As for talking to the end-user from a module, I think using carp for that is an elegant solution, especially when it's something that can be toggled on and off using a flag. For example:

package Foo;

use strict;
use warnings;

sub new
  {
  my($class, $debug) = @_;
  my $self = {};
  bless($self, $class);
  if($debug)
    { $self->{'Debug'} = 1; }
  return $self;
  }

sub bar
  {
  my($self, $hashref, @arguments) = @_;
  unless(ref($hashref) eq 'HASH')
    {
    if($debug)
      { carp "ERROR: first argument to \'bar\' must be a hashref"; }
    return;
    }
  #insert code here
  return $result;
  }
[download]

I find carp most useful for these cases. Personally I feel a module should never die on its own, that's my decision...

Remember rule one...

In reply to Re^3: Error Handling with Packages by Forsaken
in thread Error Handling with Packages by Dru

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Just another Perl shrine
	PerlMonks