What about Basic's Stop? How does that work?

Well, I believe mostly the same way.  But considering that BASIC is parsed, I would think that the parser handles all of that for you.

Quote from: Freyaday on April 10, 2011, 01:42:52 pm

What about Basic's Stop? How does that work?

Well, I believe mostly the same way.  But considering that BASIC is parsed, I would think that the parser handles all of that for you.

Yeah, the OS just ends the program the same way it ends when the BASIC parser reaches the end of a program -- it resets pointers and flags back to how it was before the program was run.

Well, if there is, you won't be able to use it in an Axe program. ASM and BASIC are very different on the calc. Using the BASIC Stop in Axe would be like using Python's sys.exit() in C.

Oh, sorry. Basically I just mean you can't use one language's routines in a different language, especially if they're run in fundamentally different ways (Axe is compiled, BASIC is interpreted).

I've decided to try to incorporate Axe into zStart. But since Axe is constantly being changed, I can't statically link to addresses within it.

So my request is a call table that's at a static location that outside programs can call. The only two calls I can see needing though are:
-Compile OP1
-Set Axe Hooks

I want the Compile OP1 so I can make a button that compiles an Axe program. Preferably, have it display everything it normally does when compiling a program, and then just return. With enough hacking, this might even allow for an on-computer compiler.

And the set axe hooks would be so that even after ram clears, you have Axe's token set.

Yes, I was definitely planning on adding hooks within Axe for external compiling.  Next update would be a good time to add them.

EDIT:  The only problem though is that Axe uses almost all of the free ram locations when compiling so you'd have to be extremely careful if you want your program to resume after the compile.

Quote from: Freyaday on April 10, 2011, 01:12:31 pm

A way to Exit the program from within a subroutine, because both Return and goto end-of-program just end the subroutine.

There's no real command to do that in ASM either. In fact, you could think of the program itself as a big subroutine that calls smaller subroutines. There's are JForce bcalls in ASM, but they leave an extra copy of the program in RAM, causing a memory leak.

There are several work-arounds. You can, for example, use DeleteMem on 9D93h and then JForce your way out of the program. (The program's size is stored in 89ECh.) The easiest way to exit an assembly program at any time is to start the program with
pop hl
ld (returnAddress), hland then quit withld hl, (returnAddress)
jp (hl)For this, stack level doesn't matter because the OS always wraps assembly code with an error handler; error handlers restore the stack when an error is thrown or you remove the handler. (Hopefully, all shells do something similar, too.) There's a specific memory address (86DEh) in which the OS stores the stack value of the most recent error handler, so you could also read that address, and then subtract the proper offset from it to get the address on the stack where the return address is stored. Of course, just throwing any error is a valid way to quit any assembly program.

EDIT: So, somebody already posted an Asm( string to quit at any time. I meant this more for Quigibo than end-users, as I think there should be an official way to quit at any time.