reported by allen (4.52 RC-1 incompatibility with 4.52 Beta version)
4.52 RC-1 is confirmed to be incompatible with 4.51
just tested with one of my scripts and no matter which one I used to tokenize with, running with it, worked fine but using the other to run, caused my computer to lock up and the script to crash.
How can this be considered a bug? AFAIK, there were never any assurances that scripts tokenized in a previous version would be forward/backward compatible.
_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.
k, assurance there might not be. at least none publicly available.
anyways, this far Ruud has done everything to keep the backwards compatibility with KiXtart, so making this one piece non-compatible would fight agains't the unwritten rule.
Since the "tokens" are the distilled core of the language one cannot reasonably expect forward or backward compatibility without adding a ton of overhead. That, and since obfuscation is deployed, the method of obfuscation should in fact mutate to make it a moving target and less attractive for someone to reverse engineer.
I think there should be a bold disclaimer that forward/backward compatibility is neither supported nor encouraged.
_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.
Registered: 1999-05-06
Posts: 391
Loc: Amsterdam, The Netherlands
Just to confirm the bug has been found and fixed.
The fixed build of 4.52 will provide downward compatibility (ie: it will be able to read scripts that were tokenized with 4.51).
4.51 will not be able to process scripts tokenized with 4.52. (Forward compatiblity, as Les correctly points out, would involve tons of overhead and in fact not always be possible.)