There is no need at all to be sorry. This is exactly why I placed this as an RFC. While your points simply enforces why I feel a solid illustration of threads is needed. Moreover, I agree that this example may not be it, but at least the topic is raised.
Next, many will say just use module X or module Y to solve this or that thread problem. However, did one really learn how to do it, or did they just learn a shortcut that they may not have in the future? Me, I prefer to learn and understand.
Finally, I have great respect for your comments and thoughts, as I see you have actually authored several write-ups. While others tend never to pass knowledge on and consistently stand in judgement of those that would. So, no apologies are needed.
--Poet
-
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.
|
