comment on

Better to be lenient in what you provide, and strict in what you permit.

Or, another way, don't let a few bad apples spoil the harvest.

As for letting /msh continue; if it's that important, where you just couldn't bear to see it public, then use email. Or IRC. Or the telephone. Or write a (gasp) hard-copy letter and mail it. Why kill the fun of the occaisional amusing accident (and I've had my share) to save you the convenience of hitting the HOME key and looking before you hit "Talk"?

- email Ozymandias

In reply to RE: RE (tilly) 1: Eulogy for the chatterbox by Ozymandias
in thread Eulogy for the chatterbox by Ovid

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.


Your skill will accomplish what the force of many cannot
	PerlMonks