Val() inconsistency (Build 255)

[DavidN]

Sorry, I don't have an example of this at the moment - I'll have to experiment around some more. As a placeholder for now - I'm noticing some strange behaviour with the String Parser in the Flash builds, it looks like it can't correctly get the last element of a tokenized list... I'll do some further experiments.

[DavidN]

Actually, I was completely wrong about the cause (it was just a symptom of the problem) - my problem was that I had left a ";" character on the end of the string, and the Flash and EXE runtimes convert mixed characters differently.

Here's an MFA showing some Val() conversions - in the EXE runtime, numbers with other characters on the end are converted as the number, and in Flash, they're interpreted as 0. 045 is interpreted as 45 but 0xFF is interpreted as 255 in both runtimes (I was impressed!)

numberwang.mfa