lets say im using axe to move a string from Str1A to an appvar. How do i find out how many bytes the string is? This is a typical text string, not limited to hex or numbers, but can range from 0 to Z.

Well, strings like Str1A aren't really variables. They're just data inside the executable, just like all the other commands, except that it's not executed as a sequence of commands. Basically, you could put random command junk in the middle of the program and call it a string.

In ASM, strings like that "end" when the TI-OS or whatever you're using to read the string hits the value 0. When you put a string by itself in Axe like

:"Hello"

all the parser does is add the sequence of hex digits [48656C6C6F] somewhere in the executable. But when you "store" it to a name, like

:"Hello"→Str1A

Axe adds [48656C6C6F00] instead (with the extra zero byte). This is because commands like Disp display each hex value as a character until it hits the zero. So if you want to know how long a string is in Axe, you just have to count each digit in the string until you hit a zero.

And, any issues with separating things with commas in that string? If yes, how should I separate them?

Sorry, don't understand there.

And, has Quigbo resolved the interrupt issue yet? The one where the Lbl was inconsistent with Goto?

No idea. I haven't exactly been keeping my version of Axe up to date, unfortunately

if you use asm to create a custom interrupt routine and keep that routine enabled when you exit to the TI-OS, should it continue to operate?

Okay, that gets complicated. First of all, many things in the TI-OS need TI's default interrupt. To give you a picture of how screwed your calc would be if you didn't restore it, these include flashing the cursor and waiting for a keypress.

EDIT: I think there's a way to have the TI-OS go through your custom interrupt, then go through its own interrupt routine, so there aren't any problems. To do that, you add a Goto 58 at the end.

Keep in mind that lowercase letters are 2 byte tokens, though, and that each will take two spots in memory rather than one.

But for strings, I think they're converted to their characters by Axe before they're added to the executable.

Quote from: DJ Omnimaga on September 02, 2010, 01:51:18 pm

Keep in mind that lowercase letters are 2 byte tokens, though, and that each will take two spots in memory rather than one.

But for strings, I think they're converted to their characters by Axe before they're added to the executable.

I am confused what you mean, could you explain in more details

Aah ok I see. I thought they would also be stored in two memory addresses. I swear there were 2 byte tokens in Axe too, though.

Whoa, can you give us the code (if it's not a contest entry)?

Okay, I see your problem(s).

First of all, you can't just move 80 bytes into Str9Y. Str9Y isn't a string; it's just a label at the end of the program. If you copy stuff over to it, you're not expanding the size of the program. You're just overwriting the data after the program, which could be bad.

Secondly, "0" is not the same as [00]. The character '0' actually has value [30], which is a problem, as the Disp command you're using wouldn't stop there. Instead, it would keep going after the "0" until it hits an actual [00].

Yeah, of course, if it's in RAM. If not, you have to change to the flash page, and I don't know how to do that in Axe.

EDIT: But most importantly, change that "0" to a [00].