Was wondering if anyone noticed the issue with Xojo 2015r3, where XojoScript changes the value of a private context property when it reads the property.
<https://xojo.com/issue/41378>
A test project is attached to the feedback ticket. Run the project on Xojo 2015r2.4, and the output is consistently 2, as it should be, run it on 2015r3 and the output value is different on each run. XojoScript basically corrupts the value of the context property on read.
The only workaround I found for this issue, is to make the property a computed read-only property in the context class.
This issue raises another question, should XojoScript be able to read private context properties in the first place?