comment on

I think it's usually obvious when someone hasn't thought things through. In your example, if the poster says "I'm writing up this bubble sort just for learning", then its clear that its not going to be used in practice and we can all safely answer the question as stated without the ingrained engineer's response of saying "That shouldn't be that way!"

However, 9 times out of 10 (I got that statistic from the same place you did), someone implementing a bubble sort is mearly naive.

A better example, which actually comes up a lot, is someone with a buggy CGI parser. The automatic (and correct, IMNHO) response is to point them to CGI.pm.

(Side point: I must wonder how many people using hand-coded CGI parsers actually understand the code they put in. Even buggy ones are a rather complex series of regular expressions and relatively deep Perl-isms. I certainly didn't understand them when I was doing it.)

----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer

: () { :|:& };:

Note: All code is untested, unless otherwise stated

In reply to Re: Re: Being helpful to a fault? by hardburn
in thread Being helpful to a fault? by graff

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.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks