comment on

As already mentioned the proper way to communiate such problems is via an exception (i.e. calling "die").

However usually the client not only needs to know that something has gone wrong, but also what has gone wrong in order to handle the error-situation.

If you communicate that with a simple string (e.g. die "error1\n") then your client has to parse the caught exception (which is then just a string) and that is brittle and silly.

A much better approach would be using exception-objects from one of the frameworks that do all the heavy lifting for you.

I have made good experiences with Exception::Class.

In reply to Re: How do I report an error back to the user of my object? by morgon
in thread How do I report an error back to the user of my object? by SomeNetworkGuy

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.


Problems? Is your data what you think it is?
	PerlMonks