... I'm definitely going to be in the habit of putting all forked code in some sort of eval block to make sure that I can
safely wrap the forking code in another eval block...
... or maybe you'd look for other ways to get the job done
without having to use "eval { ...fork... }" in the first place. I'm no
jedi when it comes to fork, but I know it well enough to respect
it, and this is the first time I've seen anyone put a fork
call inside an eval block. Just curious... what situation could make
this a preferred approach?
-
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.
|