Personally, I don’t want to see the edits that were made to a post: this is not a version-control system. However, it should be stressed (and, it is ...) that a completed thread lives on as a source of future knowledge that will be re-discovered each time it is Super Searched. Therefore, consider what the Gentle Reader™ will see at that time. Try to leave the thread as informative as you reasonably can, for someone who will encounter it for the first time (and will be able to read it, start to finish), many years in the future.
For instance, don’t remove the original question ... even if you’re embarrassed by it now. Instead, <strike>strike out the misleading or incorrect bits</strike>, and add a summary explanation. When you discover/fix the problem, add a short summary post that’s more informative and useful than just “Sorry I fixed it thanks,” and consider also adding a short note to the original-post.
IMHO,™ even though a site like PerlMonks is “a mostly-fun substitute for The Water Cooler,” its real purpose and business-value is as an information archive, which today contains a rather vast number of posts. Every thread adds to that knowledge-base. Therefore: “Please do your part. Your Gentle Reader™ will someday thank you.” (Even if you have (oops!) been smooshed by a bread-truck by that time . . .)
-
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.
|