Switch statements would be handy, but I don't know if Quigibo was still planning to add them in the future.

The labels are just names, they don't actually exist in the executable so there would be no way to tell where you actually need to jump.  ASM jumps function differently than BASIC gotos becasue the ASM uses the actual address in memory which varies wildly as your code grows and changes.  I'm still trying to see if switch statements will be possible and save memory by the way, but I would need to add a break command or something which would be a lot of work.

The reason I don't have 8xY sprite drawing is because it will either make the existing routine larger and slightly slower or i would have to add a whole other sprite routine.  It gets complicated due to the clipping.

I'm still trying to see if switch statements will be possible and save memory by the way, but I would need to add a break command or something which would be a lot of work.

You could possibly make Return break out of the switch statement (which could possibly be the smallest solution -- just 4 bytes to push the return location onto the stack and 1 byte per return, as opposed to no overhead and 3 bytes per break)

Such sprite routine might be good, unless it really signifiantly make your program grow much larger (like 70-100 bytes larger).

calc84maniac, I was thinking about that, and it's a great idea!

I also thought of an interesting new block type which is basically an anti-subroutine.  Instead of calling a routine and then returning from where you called it, you tell it the place you want to return to and then do the routine.  I'm wondering if that would be useful because I do that a lot in the actual parser code.  In Axe and assembly, it's basically this:

SetRet(LBL)
...
Return
...
Lbl LBL

  ld de,LBL
  push de
...
  ret
...
LBL:

The switch statement itself would use something similar.  And since the return point is set to the end of the switch statement, I wouldn't need to add a new break command, you could just use "Return".  The main problem though is that this would actually create memory leaks if you tried to do a goto out of the switch statement from within the switch statement.  I think a common use of switch statements is branching to a bunch of labels though so I'd have to figure out another way to do that...

Yeah, I've already added that

But note that it will only make your program larger if you want to use it, and if you dont want the size increase, you can stick with the normal routine and just use two or more 8x8

One concern I got, though, is if you use both 8x8 and the others, wouldn't both routines be added? That might waste a bit of space