In the event of something happening to me,
There's a soiled paper napkin I'd like you to see,
It's the documentation for a program that grew.
Have you seen the source code Mr. Jones?
Do you know what it means on the inside?
The LOC count is huge, it's one massive kludge
Mr. Jones.
I keep straining vi refactoring it out
Maybe move some of this parsing code around
Or say to hell with it and put away make(1)
Thinking instead I should go and play quake.
Does the input validate Mr. Jones?
Does it take tainted data from the outside?
If it don't end in 0, the buffer will overflow,
Mr. Jones.
In the event of sense entering this company,
I'd like us to use something better than C,
There's a language called perl licenced Artistic and GNU.
Have you seen my camel book Mr. Jones?
I'll take either the pink or the blue one.
Interpreters rule, and regexes are cool.
Mr. Jones
-
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.
|
