1Tim Tripcony  25.08.2010 14:20:40  Don’t forget the radix

While unrelated to the point of your post, I wanted to caution you about the behavior of parseInt: you should always supply the radix argument to ensure it's using the numeric base you intend, e.g.:

var Statusnumber:int = parseInt(Statustext, 10);

Without the radix, it will always give you base 10, which is nearly always what was intended, until it ecounters something like "08", which it will assume you want treated as octal.

2Paul Withers  25.08.2010 14:37:56  I agree about testing

Yes, I'd strongly recommend testing. There seem to be a few areas where you could code things incorrectly in earlier versions, but they worked. Because of limited documentation, there was nothing to tell you they were wrong or what the correct was. An example I've had was in try...catch(e), using e.getMessage(). It worked in 8.5.1, but the properties and methods were never documented and didn't seem to correspond to what I could find documented for Java or Javascript. e.toString() seems the most reliable method I've come across.

With regard to parseInt, I tend to use @Formula equivalents where possible, so @Integer. Hopefully that doesn't get hit by the octal problems, which I've been burned by before when doing date handling in javascript.