A new RPL firmware for the 50g

[Claudio L.]

(01-03-2014 05:25 AM)David Hayden Wrote:  Something that Bruce and I talked about was an RPL optimizer. It could replace stack manipulations like Pauli suggested, along with things like built-in constants. But the real benefit would come from knowing the stack diagrams of the entries and analyzing the types and number of values on the stack. For example, if it knows that the previous execution put two REALs on the stack and the next instruction is the UserRPL "*" command then it could replace that with %* (the SysRPL command to multiply two REAL numbers for readers who don't recognize it). I'm sure there are all sorts of other optimizations that can be made.

With the speed of C implemented routines, we probably won't need this type of optimization. But I always thought that there should've been a flag in userRPL to turn on/off argument checking, so when you write a complex program, you check your user arguments first, then disable checking for all your internal calculations, where you know the arguments are good.

Claudio