“++”, Mr. Mischief: Do Not Do A Thing Already Done.™ This ol’ world is positively stuffed with people who have faced this exact same problem, and who have solved it, and ... who have very-graciously shared their tire and rim shops.
When you are faced with a problem, of course(!) it is natural to assume that you are the first – that you must now solve it (from scratch). (And indeed, perhaps you subsequently do just that! “Woo, hoo!”) But ... a perhaps-more-seasoned approach to the same scenario might be this: “this smells like a vintage™ problem ...” Therefore, instead of reflexively starting right out by writing source-code, let’s instead step back and do a little “due diligence.”
Yeah ... unfortunately, there are no bonus-points for too-late discovering that you have just wasted a substantial portion of your own time, “if only you had known.”
-
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.
|
