#2 Use Colin's first-char approach to grab each char & then use that as an index into the prooList to get it's charToNum()
That wasn't my idea, but even so, the lookup table only gives a slight speed increase because it's the string[i] part that is slow, not the chartonum() part.
But wait, I tested it anyway, and it turns out that the property list lookup to save doing chartonum() ends up taking longer than just doing the chartonum, so no prize for Buzz at all!
[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
