Is there a way to have Axe programs stay the same speed when transfered from an 83+ to 83+SE or 84+/SE?

I don't have the Full command anywhere in my code, but now that I actually think about it, my Archive space is nearly full would that maybe have something to do with it? Because I sent it to another 83+ and it ran faster on her calc.

I don't have the Full command anywhere in my code, but now that I actually think about it, my Archive space is nearly full would that maybe have something to do with it? Because I sent it to another 83+ and it ran faster on her calc.

Strange, this shouldn't be happening. What is the person's OS? If it's a TI-Nspire, then this is why, though (because the Nspire won't emulate 84+ ASM programs at the right speed)

When the calc is set to 6 MHz, is it set specifically to 6 MHz directly or is it set to 2.5x lower than its regular speed? (example, if the calc is 15 MHz, it will be set to 6. If it's 20, then it will be set to 8. Is it how it works for overclocked calcs?)

If she didn't overclock it, maybe she got it from someone who did, too.

^
That feature is a bit overdue, but its definitely deserved.

Congratulations on the feature!  Axe is still highest rated program i see :] and with 15 votes thats not too shabby! In fact that it excelent!  Especialy for a 9.88 rated review!  Go Quigibo!

I think that might be what convinced them to feature it actualy.  Props to Dj too!

Hello,

I just saw Axe on ticalc.org. At the moment I don't have a physical calculator to test with, nor do I have a ROM dump on this machine. My comments are based only on the text in "Documentation.pdf". Here's some feedback on it:

Pointers (page 9)
"The 0th byte has the address 0, the 1st byte has the address 1, all the way up to the last byte with the address 65536."

Minor nit-picking:
Actually, there's no such thing as "the zeroth item"; the correct way to say this would be "the first byte has address zero, the second byte has address one". Not exactly intuitive, I know. If you don't want to change this I can understand.

Actual error:
The last byte has address 65535.

Data & Arrays (page 11)

"Disp {A+GDB1},i"
It might be easier to understand to write "GDB1+A" (assuming that Axe understands this; I didn't check, but assume it does). I understand the current notation is not so much wrong, but it could be unclear for beginning programmers.
Since you are very consistent about this notation, I assume there's a reason for it... performance? Can Axe optimize "A+GDB1" better than it optimizes "GDB1+A"? If so, maybe you should explicitely state both are valid, but "A+GDB1" is slightly faster.

"We use the curly brackets to indicate that we want the byte that's at the address of the pointer, not the the value of the pointer itself."
From reading your code samples:
Disp Str1        Displays the contents of the (probably zero-terminated) string starting at the address in Str1.
Disp {A+GDB1}    Displays the value of the single byte at base address GDB1 incremented with offset A.
That's quite a difference from what you're saying in the documentation...

Data & Arrays (page 11)

The comments for one of the pieces of sample code say "BAISC", oops...

An Example Program (page 14)

You're already using the "optimized dual-store":
0->S-1->D
This hasn't been explained yet and is hardly standard notation. Putting a note "see page 17 for details" would be helpful.

Optimization tricks (page 17)

"Evaluate all constant expressions before compiling."
It would be very awesome if you could teach Axe to recognize expressions working on two constants and automatically decide to pre-compute them...

"If the last line of your program is Return, then remove it. Even if it was part of a subroutine, the return is automatically added at the end for you so there's no need to have 2 returns at the end. Saves 1 byte."
Uhm, that saves 1 byte in the source, not in the executable, right?

And about commands.htm:
Fix CODE: Changes how text is drawn. Code must be a constant.
Wouldn't it make more sense to make CODE consist of flags? That way you can set multiple values at once. Especially useful if you want to reset everything at the end of your code.

ReturnIf EXP
Is there a special reason to include this? It seems to be equivalent to If EXP Return End.


Cool project!