Your advices are low quality.
- What should eb done for step 5? Its frustrating. For sure, there will be many breaks on that step.
- Are you sure you have minimal set of downloads to do the task? For sure, the task could be performed with much less amount of garbage.
- In case you beleive you add something usefull, why not proposing appropriate documentation patch to perl5developers? (AFAIK there were some postings in p5p recently about your topic)
There are resaons why I do not insert tips for, say, compiling Perl for WinCE devices, despite of fact those could be useful because of growing amount of WinCE users roaming around. Those belong to their place.
My point of view -- your posting must go to p5p and not 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.
|
