comment on

Side question: I'm currently debating with myself over when it's appropriate for a method to report an error to STDERR on its own instead of just passing back an error code to the caller and letting them decide whether to report it or not. Thoughts?

I believe that most of the time, methods within a module should not screw around with their environment. However, if reporting to STDERR is seen as convenient, I prefer a module that will provide a switch to turn STDERR reporting on or off, defaulting to the off state.

When I encounter a module that insists upon spewing at STDERR, I add to my own code a method for redirecting STDERR to /dev/null, and turn it on at the same point at which I comment-out the uses of the strict and diagnostics pragmas.

I think that by providing the switch in your modules, you allow your user to operate more completely within TMTOWTDI space.

In reply to Re: Re: Thoughts On Object-Oriented Module Design. Input Sought. by gloryhack
in thread Thoughts On Object-Oriented Module Design. Input Sought. by ajt

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.


Do you know where your variables are?
	PerlMonks