comment on

Our platoon had been in directory for six months. We got orders from the kernel to proceed to the ../combatzone. We went into the code jungle. Corporal Lint was walking point, but we had air support from the 111th ddd division.

Suddenly, the bugs were all around us--they'd been hiding in a thick growth of inodes, wearing special dot-camoflauge so they looked like "." and ".." Private A. Out took the first hit, a segmentation fault that, as is so often the case, proved immediately fatal. Our group started losing morale, and we started to retreat, but ahead we saw the sign:

use warnings; 1 km

use strict; 1.1 km

Lieutanant Perl took command, and led us to safety through the binary jungle. Soon, we had our casualties safely under the care of the Perldoc, and were busy splaining the problems we'd encountered in the operation. Because of his quick thinking, the lieutenant was promoted to 6.0

$jPxu=q?@jPxu?;$jPxu^=q?Whats?^q?UpDoc?;print$jPxu;

In reply to Re: Programming is combat by Ambidangerous
in thread Programming is combat by brian_d_foy

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.


No such thing as a small change
	PerlMonks