Something that could be useful would be the ability to manually backup an archived source.  It gets kind of tiring having to unarchive every time I want to backup (at least, for the on-calc way)

EDIT: (quote from zstart thread)

A bug: using the on+enter shortcut to compile disables the auto-backup feature, because

Quote from: thepenguin77 on IRC

[18:27:38] <thepenguin77> [...] when compiling from the API entry point, the option is changed

Afaik, this would need the entry point to be modified to have another input...

Also having to do with the backup feature, a fix for ^

Reading labels as values is for sure coming in the next version.  But its mostly for Axioms that require labels as arguments because there really isn't any other use for them since you still can't jump to arbitrary values due to leaks and unsafe code.  I think I might have a way to allow programs to exit anywhere soon, but I already have to rewrite half of the parser from scratch so I doubt I'll have time next version.

For those other assembly commands, most of them are really too specific and low level for any general use.  Runer112 actually made an LCD Axiom LCD Kit that does most of those already and you could certainly design a port axiom to allow arbitrary port writing, I just don't see the purpose of that for the average game.

The ability to jump code execution to an arbitrary location.

You can do that with Asm(9E):

Quote from: calc84maniac on November 04, 2010, 08:07:24 pm

Quote from: Deep Thought on November 04, 2010, 08:02:16 pm

Oh, and

• Allowing jumping to an arbitrary place in memory

That can be done using a simple Asm(E9), which will jump to the address of the last result

In other words, E8000:Asm(9E) jumps to $8000.

Look closer, it's actually E9. 9E is the SBC A,(HL) instruction.

So I'd do GetCalc(code):Asm(9E)?

E9, as calc84maniac said.

But it's not that simple to jump straight to a different program. Remember you can't execute code beyond the hex address $C000 (that's why programs are limited to 8811 bytes, since 8811 is the difference between $C000 and $9D95, where programs normally start). Unless you're absolutely certain the program you're looking for isn't beyond $C000 (which is perfectly possible), you have a pretty high chance of getting a RAM clear with that code.

In addition to that, all programs are assembled to run at $9D95. Run it from anywhere else and all of the absolute pointers (which is almost every pointer in Z80) will be wrong.

And what's the asm for that, and can I execute code within an appvar?

I was wondering...the ability to use ! just before a var or whatever to check if it's false.  ie instead of having to do
If getKey(15) and (A=0)
...it would be possible to do something like...
If getKey(15) and (!A)

Or is VAR=0 already an auto-optimized thing?

It's already optimized, but not as much as if you did
If getKey(15)
!If A
...
End
End

because it has to calculate the 0 or 1 boolean in order to perform the AND.