In fact 1 (integer one) is by definition NOT a prime number<div>see <a href="http://primes.utm.edu/">http://primes.utm.edu/</a></div><div><a href="http://primes.utm.edu/"></a>and for the first prime numbers: <a href="http://primes.utm.edu/lists/small/1000.txt">http://primes.utm.edu/lists/small/1000.txt</a></div>
<div><br></div><div>Bye</div><div>Enrico</div><div><br><div class="gmail_quote">On Tue, Mar 9, 2010 at 11:36 PM, Chris Cunnington <span dir="ltr"><<a href="mailto:smalltalktelevision@gmail.com">smalltalktelevision@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Sigh. Premature send. <div><br></div><div>My point is that isPrime in 3.10.2 would always give an error if sent to a 1.</div>
<div><br></div><div>1 isPrime </div><div><br></div><div>produced an error. That was what I was seeing. Now, with a great, new Trunk isPrime, I can substitute and it works as expected. </div>
<div><br></div><div>Sometimes it's not me. And the Trunk code rocks.</div><div><br></div><font color="#888888"><div>Chris </div>
</font><br><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Enrico Spinielli<br>"Do Androids dream of electric sheep?"— Philip K. Dick<br>"Hear and forget; see and remember;do and understand."—Mitchel Resnick<br>
</div>