Return an error value. If it's really, really important,
write a message to STDERR or a log file (not STDOUT!). Library code
should never, never, NEVER die on any error
condition short of the CPU bursting into flames (and even
then it's questionable). What you consider to be a
fatal error may be a normal condition for the programmer
using your library/module. (Yes, I've had the supreme
displeasure of using a library which "helpfully" terminated
my programs whenever an error occurred without giving me a
chance to detect and correct the situation, or at least
perform a controlled shutdown.)
Oh, and another thing re: the examples under question 4 -
the user should never be subjected to detailed information
about the programmer's mistakes. It will just confuse them.
(*ring* *ring* "Hello, tech support." "Your program just
said, 'Wrong number of parameters! Correct syntax is
my_sub($name,$phone,$address)', but I filled in all the
blanks on the form. And WTF does 'my_sub' mean?")
-
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.
|
