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...

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.