comment on

There always seems to be a background of chatter about how Perl makes it easy to create bad programs, and quite honestly I've never really dissented from that view: there is a lot of horrible, insecure and badly written code out there.

However inspired by Bugle I thought it might be interesting to see just how much bad stuff there really is. Of course there is always the "low hanging fruit" of code using horrid cut and pasted parameter parsing which always contain so many other ~~lovely~~ bugs. Then I turned to passing unchecked form input as a header to a mail program. Eugh. Passing unchecked input to system anyone? Anyway I wanted to try something like "open OUT ">$In"" filetype:pl to try for unchecked input being passed to open but it made too many false positives

Anyway I got bored at that point, however I thought it would be amusing to set you lot on it to see if we could come up with some examples of searches that are guaranteed to throw up the most egregious Perl code on the web.

To it!

/J\

In reply to Mad, bad and dangerous to know by gellyfish

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