multiple + other -- most of those would influence whether or not I use it. And a few other influencing params:
- it works for me
- it's the only interface (or most-readily available interface) for an external library
- using the approximate solution found in the CPAN module was easier than coding a whole exact solution by myself
- using the premade solution had better edge-case coverage than what I came up with
- which criteria was used depended on the exact specifications for the code being developed
- it works on Windows with Strawberry Perl, not just on linux
→ aka "good cross-platform compatibility"
- it works on an ancient machine with perl v5.8 (or preferably v5.6)
and though this hasn't influenced me yet, I know it does some monks:
- it's small enough to fit on (insert favorite small embedded system with a tiny perl here)
-
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.
|