I have a list of feature requests here. Don't feel like you need to include all, most, or even any of these, as I and others can get by without them, but they would be nice. I'll list them in descending order of a combination of how much I would want to see them added and the probable ease of implementation:

• InsertMem and DelMem bcalls. They would be invaluable for editing variables with a large amount of data in them. (If anything, this is the feature I would want the most, and it seems fairly easy to implement)
• Case statements.
• Reading from/storing to the Ans variable for things other than integers (namely strings).
• Dialog (menu) bcalls.
• General bcall support.

EDIT: Wow, how did I miss this: the Line() command working on back/arbitrary buffers. The routine's already there, it's gotta only take like 10 seconds to modify it for this. I hear you already did it for the pixel commands, which is good.

Quote from: Runer112 on October 07, 2010, 09:19:29 pm

I have a list of feature requests here. Don't feel like you need to include all, most, or even any of these, as I and others can get by without them, but they would be nice. I'll list them in descending order of a combination of how much I would want to see them added and the probable ease of implementation:

• InsertMem and DelMem bcalls. They would be invaluable for editing variables with a large amount of data in them. (If anything, this is the feature I would want the most, and it seems fairly easy to implement)
• Case statements.
• Reading from/storing to the Ans variable for things other than integers (namely strings).
• Dialog (menu) bcalls.
• General bcall support.

All b_calls can be accessed with Asm(EFXXXX).

I support using Ans for strings! It'd be really helpful, and I have no idea how to do it myself.

how might we use this? for example, i see insertmem is 42F7h. so Asm(EF42F7) would run the bcall, but how do you write to the registers? since HL is the amount to add, and DE is the address at which to add? also, what if there's something important in HL or DE?

In Axe you can only set hl, which contains the current value in the calculation. de is used sometimes in two-argument instructions, but that can't be done with Asm(.
Also, due to endianness, it would be Asm(EFF742), not Asm(EF42F7)
Edit: semi-ninja'd

i'd assume anything you can do in asm you can do with asm().... also, would i need to then push every register onto the stack and pop them accordingly after the bcall, since insertmem destroys all registers? yeah... i would like insertmem+deletemem support.

i'd assume anything you can do in asm you can do with asm().... also, would i need to then push every register onto the stack and pop them accordingly after the bcall, since insertmem destroys all registers? yeah... i would like insertmem+deletemem support.

I guess they would make nice features, but should be highlighted in the docu as very advanced features.

The Ans variable should be accessible already with "Ans"->Str1 just like you read other OS variables.

bcalls aren't useful to implement becasue of the reasons you're discussing now.  bcalls require very specific register input and very specific register output.  There wouldn't be an easy way to translate that directly to Axe syntax.

InsertMem, DelMem, and EnoughMem are possible, I will look into some good tokens for them.

There is no bcall for making menus as far as I am aware.

EDIT:
Also, the line routine is not hijackable, so it would have to be an entirely different routine for the back buffer or a more inefficient routine for arbitrary buffers.  Same thing with the circle command.

I may support 8xY sprites, but I'm not sure yet.

The Ans variable should be accessible already with "Ans"->Str1 just like you read other OS variables.

GetCalc("Ans") returns 0 for me whether I use the Ans token or spell it out. Also, I believe storing strings to Ans involves a more complex method in which you need to create a temporary string variable in which to store the string, and then store that variable's name in Ans.

There is no bcall for making menus as far as I am aware.

Is this not it?

Ah ok. What does change location accross OS versions? Mapar007 told me about the Garbage Collecting routines.