I'm completely stunned that you'd suggest not
using regexes for parsing. They might be hard to get "right", but I assure you, getting the same effect with ord
is going to be a struggle you don't want to pursue.
Peer review and a huge number of test cases, especially those culled from real-world experience, can help make your validation routine more robust. For example, check through your current database and make sure everything passes before unleashing your validator on the Web site. It's really unpleasant to find out that Really Important Customer XYZ can't post their Really Big Order because their part number has a dash in it, and your validator rejects that as invalid.
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.