lest someone see your bad code and not notice the correction.

Respectfully I suggest you go reread the very first response to your "correction". Your first response didn't do a very good job of discouraging reuse of the "bad" code so perhaps you should rethink your strategy. Friendly advice: If you want people to take you seriously, then give a reason why they should follow your advice.

I think that increasing the "volume" of your objections just makes it more likely that the recipient will become defensive, making it harder for people to take them in. Since this comes up over and over and you reply to it over and over, please, take a minute and put together links to previous discussions of it so you can reference that the next time (you can build up this node or web page as time goes on as well, so even one link would be a useful start). This has been suggested several times before but I have yet to see it done.

You seem to really take this cargo cult problem seriously so I don't understand why you don't take the time to address it a more effective (and polite) way.

There are constantly going to be new Perl Monks and, being new, nothing we do here is going to change much about the ideas and attitudes they start out with. So we mostly just have to adapt to them.

        - tye (but my friends call me "Tye")