I guess a factor in determining intended complexity may be the intended audience. For me, that audience is the non-Perl programmers who will inherit the code when my contract is over. Even though most of what I write is only for my use (that's how I sell it), I leave the code behind when I leave the contract, but with the hopes that someone else will look at it and try to use it. I want to make that use as easy as possible for them. If I were writing a module for CPAN with the intended audience being other Perl developers, the intended complexity level could safely jump way up.
-
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.
|