I also enjoy this idea. I've asked for code optimization advice on some stuff that I've posted, but I rarely get answers that cover optmization per se. I'm finally at a point where I feel comfortable working in Perl and need to move to the next level, so to speak. While much of that is learning the libraries and not constantly reiventing the wheel, a lot of that is understanding what's under the hood so I'm not putting a Ford Pinto engine in an 18-wheeler.
Update: Adam did rightly point out that my metaphor was rather lame. I knew it was when I typed it, but it's akin to how I speak: I just open my mouth and wait to see what comes out.
-
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.
|
