comment on

I'm afraid I don't get this (maybe because I'm not an avid follower of the CB?). Why on earth should one not want to put pipes in a data field? Unless, of course the fields themselves are pipe-separated...

\| # <- Ceci n'est pas une pipe

Update: Just to be clear: my post was not meant to be taken as Lady Aleena bashing (which, BTW, seems to be the preserve of Anonymous Monk). Rather, it was meant to be a request for some context:

From the OP:

I said I would never use pipes in my data fields. Tonight I did. Now I am feeling more than foolish. (And I've made more work for myself while trying to make less work for myself.) I just learned my lesson.

For me, this makes little or no sense out of context. Context that was presumably present in the Chatterbox ('I started this thought in the CB'). Context that should be provided in this thread, in order to make sense of it and to make the OP worthy of Meditations status.

In reply to Re: Never say never by Not_a_Number
in thread Never say never by Lady_Aleena

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.


"be consistent"
	PerlMonks