Under OS 2.54 MP, everything runs at the exact same speed as on a regular 83+. In 15 MHz mode, the speed increase is much lower than it is on a real 84+, though.

Older Nspire OSes got incredibly slow speeds at times with ASM stuff.

that would be really easy to write in Axe! just send the info of the program first using the Send Command, while the other Calc is in Get()-mode.

I would do it this way:
1. give the sign: "I'm ready to send a program" with a certain command,
2. then send the length of the name,
3. then the name itself char by char,
4. and then perhaps the type of the data (prgm, locked prgm, appvar,pic etc),
5. and last but not least the data of the program itself.

I am willing to write this routine this evening, but not jet (it's just 16:00 o'clock over here)

@ calc84maniac: Nice

@LordConupiter: Not 2 calc data sending. I'm talking about having the ability to run other programs from an Axe compiled program.

@LordConupiter: Not 2 calc data sending. I'm talking about having the ability to run other programs from an Axe compiled program.

did you mean that! sorry, I misinterpreted your Post, for U suggested to use the Get command, and that's already used for data transfer between 2 calcs.

@Runer: how did you do that! those two code block next to each other?

Quote from: ACagliano on October 05, 2010, 09:56:56 am

Feature Request:

TI-Basic has the ability to transfer control to another executable, then return when done. Axe should be able to do the same. Maybe, use the command Get( or something, where the command

Get(prgmAAA)

would cause the executable to transfer execution to the asm program AAA, then return to the main.

If you want to call another Axe program, unless you desperately need them to be two separate compiled programs, this can already be achieved with included programs. Just call it as a subroutine in your main program without a Return, like this:

Code: (Your main program) [Select] .PROGRAM ClrHome Disp "Hello " sub(A) Disp i Return Lbl A prgmINCLUDE

Code: (prgmINCLUDE) [Select] .. Disp "world!" Return

@Runner: That method includes the CODE making up the included program and still compiles as one program. Think of what happens in the TI-Basic code

Disp "Hello"
prgmZCLRHOME
Disp "Goodbye"
I'm suggesting Axe have a way to do that. Like what calcmaniac said, using B_CALL ExecProg

Execlib only exists on 84+ OS, and only starting at a certain version I think. Not a good choice, I'd say.

I think this is very difficult to accomplish.  In order to run a program, it must be copied into 959C.  Unfortunately that is where the current program already is, so you would need a 3rd piece of code that would copy the original program back into its original RAM space, copy the second program into 959C, PUSH a piece of its own code onto the stack so that when the program exits, it is able to copy the original program back onto 959C

I think this is very difficult to accomplish.  In order to run a program, it must be copied into 959C.  Unfortunately that is where the current program already is, so you would need a 3rd piece of code that would copy the original program back into its original RAM space, copy the second program into 959C, PUSH a piece of its own code onto the stack so that when the program exits, it is able to copy the original program back onto 959C

But how would TIOS do it then? subprograms can be called in BASIC, or do BASIC programs not have to be copied to 959C?