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
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,
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.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||