<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<blockquote cite="midm2fyjyt1dw.fsf@bese.it" type="cite">
<blockquote type="cite">
<pre wrap="">* Russ' regex validator, an improved email validator, and a phone-number
validator based upon it.
</pre>
</blockquote>
<pre wrap=""><!---->
nice. are we sure cl-ppcre and javascript have the same syntax for
regexps?
</pre>
</blockquote>
The ECMA spec (at least this one from 1999:
<a class="moz-txt-link-freetext" href="http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf">http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf</a>)
says on pg 141, section 15.10:<br>
<br>
NOTE<br>
The form and functionality of regular expressions is modelled [sic]
after the regular expression facility in the<br>
Perl 5 programming language.<br>
<br>
So... I take that to mean javascript regexps have the same syntax in
most cases, but don't be surprised if esoteric stuff breaks.
<pre class="moz-signature" cols="72">Ryan Davis
Acceleration.net
Director of Programming Services
2831 NW 41st street, suite B
Gainesville, FL 32606
Office: 352-335-6500 x 124
Fax: 352-335-6506</pre>
<br>
<br>
Marco Baringer wrote:
<blockquote cite="midm2fyjyt1dw.fsf@bese.it" type="cite">
<pre wrap="">"Nathan Bird" <a class="moz-txt-link-rfc2396E" href="mailto:nathan@acceleration.net"><nathan@acceleration.net></a> writes:
</pre>
<blockquote type="cite">
<pre wrap="">Number-range-validator should inherit from is-a-number validator, it doesn't
make sense to check if a string is inside a number range, and so we've got
to do the work of ensuring it is a number first anyways. Previously this was
being handled kindof by parse-integer (would return nil or any integer found
in the string), and would break for number range validator (I expanded the
examples/forms.lisp in order to show this)
Is-an-integer-validator previously allowed 11.3 without giving any error and
returned value 11. It now fails the is-an-integer validate.
</pre>
</blockquote>
<pre wrap=""><!---->
nice. applied everything.
</pre>
<blockquote type="cite">
<pre wrap="">Things I came across but didn't change:
(value number-field): if the client didn't enter anything in, shouldn't we
return nil and not 0?
</pre>
</blockquote>
<pre wrap=""><!---->
yes.
</pre>
<blockquote type="cite">
<pre wrap="">I don't think there is a need for the integer-range-validator anymore.
Number-range-validator takes care of it, and if you are using the
integer-field you already have the is-an-integer-validator attached.
</pre>
</blockquote>
<pre wrap=""><!---->
agreed.
</pre>
<blockquote type="cite">
<pre wrap="">Adding a 'required' initarg (that is itself optional :-) to form-field to
automatically attach the required validator to anything. This is such a
common case we probably want to make it easier.
</pre>
</blockquote>
<pre wrap=""><!---->
agreed.
</pre>
<blockquote type="cite">
<pre wrap="">The javascript validation is still untested, but was broken previously do to
an id mismatch (at least on the examples page). I will try to look into this
further somewhere in the near future.
Buy now (from ucw_public) and you ALSO GET!
* a second patch where I rearrange the file a bit to try to reduce the
number of style-warnings due to undeclared functions.
* more documentation
</pre>
</blockquote>
<pre wrap=""><!---->
much abliged.
</pre>
<blockquote type="cite">
<pre wrap="">* Russ' regex validator, an improved email validator, and a phone-number
validator based upon it.
</pre>
</blockquote>
<pre wrap=""><!---->
nice. are we sure cl-ppcre and javascript have the same syntax for
regexps?
</pre>
</blockquote>
</body>
</html>