and I don't see that as a bad practice. Works like expected and is documented. The alternative would be to shove the result explicitly through three other subs:
$thingy -> foo (1,2) -> to_output_channel;
$string = $thingy -> foo (1,2) -> as_string;
@lines = $thingy -> foo (1,2) -> as_list;
which gains me what exactly?
It gains you
- explicit clarity of intent
- 3 parameterizable output methods
- 3 methods which can be re-used or overloaded as needed
- The ability to call all 3 output methods, none or any combination simply by mixing/matching method calls.
Should I avoid localtime and roll my own?
Well, no. Try Date::localtime or Time::Local or anything in the DateTime hierarchy.
Carter's compass: I know I'm on the right track when by deleting something, I'm adding functionality
-
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.
|
