Quote from: E37 on November 03, 2015, 07:54:13 pm

I must be missing something on the >Tok command. When I ask it to display {A} (or {A}r) >Tok, it displays a completely different token.

The OS calls for displaying tokens require a pointer to the token to be displayed. And Axe uses these calls to implement ▶Tok, so the same applies. I presume this decision was made because tokens are almost always displayed as part of a program or string in RAM, and putting the read in the call saves callers from having to do so. Since you're also editing a program in RAM, this decision should actually make your code simpler. Just drop the curly brackets for the memory read.

It works! Since I can use the tokens directly I am definitely using the tokens instead.
How would I write tokens back to the program? "token" -> A doesn't work

Does anyone know if writing to archive is bad for the memory?
I have heard that repeatedly writing to archive will eventually damage it.

On a different subject, how do programs like Doors find the names of all the programs (and how can I do that in Axe)?

I have decided to go ahead with the small font program editor. So far I have have figured how to convert back and forth form decimal and tokens (If  = 206).
I am not sure whether to go with writing out programs by letters (which would be easier to display and make the editor smaller) or by tokens (which would make the editor much bigger but the saved files smaller).
It looks like reading and writing the programs will be the hardest part (so I can compile code written in the editor or edit it in the basic editor also).

It would be really cool if it could display code like "{L1 +8}" as "boss1hp" if the user declares the name. That way variables can have really long custom names and there (theoretically) is not a name limit.

Any ideas (or ways to do any of this) would be awesome!

I am writing a program to restore some of my files (after RAM clear thanks to zStart) and I am using the copy command.
Does the size command {pointer-2} not work of files? It works fine if I just manually input the size but otherwise it just copy's one bite.
On a different subject is there a way to run already compiled programs (including the ability to call subroutines) to bypass the compiled code limit?
I know about axioms to circumvent this need but I would like to not have to use them.

For self modifying code what numbers correspond to which command tokens?

On a different subject, I noticed that the Text( command behaved weirdly when performed off screen.
Could this just be my bad code or is it something else?

Also, what exactly does #Relloc( do? (I know it moves the location of something, but why would you want to do that?)

Quote from: E37 on October 27, 2015, 06:28:06 pm

Yes, I am trying to convert compiled asm code to hex to run in Axe.
I just used to power off feature as an example.
I am also just trying out different commands. I never know when this knowledge might be useful! 

Then you'll want to use this tool to "unsquish" the program into the hex bytes.

Thanks!
Do you know how to enable the small font on zStart?

Thanks! All I was trying to do was enable the small font size editor.
I looked through zStart (I already had it installed) and I couldn't find how to enable it.
Also, I heard it could let you jump to labels and couldn't find that feature either.

---

On the subject of reading files, I've tried to convert compiled programs to hex using the >Hex command.
I got the program to work but the code doesn't work.
Is it possible to convert a compiled program to hex?
I want to run some asm commands in Axe that don't exist (like powering the calc off).

_{Edit (Eeems): Merged double post.}