In Axe, lots of commands use r's, so for example:

DispGraphr
DispGraphrr

(3 and 4 levels of grayscale)

A->{H}r
A->{H+1}r

(pointers)

When I compile programs that use r'ed stuff in WabbitEmu, it returns no error and works

However, in my calculator, it gives me syntax error in all r's, I use an 84+ keypad, is it a bug?

Let's blame 2.53MP again

I type normal r, since I can't do the upper r in the calculator :S

I type normal r, since I can't do the upper r in the calculator :S

They are two totally different tokens, so you have to use ^r. It's under 2nd+[ANGLE] > 3, as nemo said.

Quote from: ScoutDavid on December 18, 2010, 05:37:40 pm

I type normal r, since I can't do the upper r in the calculator :S

They are two totally different tokens, so you have to use ^r. It's under 2nd+[ANGLE] > 3, as nemo said.

That explains it all

It appears so. Some people seem to have fallen in love with some of the new math functions and some even worship 2.53 MP despite all the problems and slowness it comes with. It is so bad from a developer point of view that now you have to test your programs in both 2.43 and 2.53 MP to make sure they work. With older OSes, we rarely ever needed to do that.

Anyway when many people upgrade to the latest version of something then immediately try to downgrade, it shows there's a serious problem with the latest version. I can understand if it's a beta, but not a final release. X.x

I heard it is worse in terms of stability but mathprint mode is slightly less slower

Most likely emulation.