0 Members and 3 Guests are viewing this topic.
If you look carefully at that line, you use a right parenthesis instead of a right curly brace, hence your problem. Interestingly enough, I could figure out this exact problem just from looking at the hex error dump. Boy am I glad I added that.EDIT: Also, Builderboy is absolutely correct about what he mentioned in the post below. Adding the store there will actually introduce issues because of how the increment operator works.
It's also worthy to note that the ++ operation already stores the incremented value back to where it was read from, so the →{C+D}r part is completely unnecessary (and may not even work 100% of the time, since ++ doesn't always return the incremented value)
In other news, Frey continues kicking unprecedented levels of ass.
It seems that For(12)r doesn't work for me → INVALID TOKEN right on the r.
:.TEST:2/10->Float{C}:C*10->C:Float{C}:Disp C>Dec
1Done
0 Done
Yeah, I'm not surprised floating point math isn't working, because Axe doesn't have floating point math. The float{} command is only for converting between OS floats and Axe's standard 16-bit integers.However, if you want something slightly closer to floating point math than integer math, you can use fixed point math. Standard fixed point numbers in Axe give you a range of about -128 to 128, with a precision of 1/256 (they're essentially signed integers treated as being a fraction over 256). You can find more information about both float{} usage and all the fixed point operators in the Commands.html file included in the Axe download.
:.TEST:(1/*10)**10->B:Disp B>Dec