Then again by becoming fluent in Perl you to some degree pick up *NIX knowledge. Or at least you get some exposure to it.
Perl internalizes a good bit of "The *NIX Way" to do things (e.g. file and directory handling, large bits of the POSIX API, the socket API) and by learning to use Perl you're going to look at problems through the prism of that philosophy (pardon me while I run my metaphor through this wood chipper over here a couple more times . . .). Granted while lots of Wintendo specific things don't exactly fit into the same conceptual framework (driving stuff through OLE, for instance) or work as well (processes and fork() versus a thread based model) the underlying basics translate fairly well.
-
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.
|
