Well, all MirageOS/Ion programs have a description of some sort, even if it is empty. So perhaps in that case you would do: .prgmName "" [spritedata]

Oh, I like that idea!
But we need to make sure that it keeps compatibility with old programs.

I like that!
I also really want to define the type in the header.  I've compiled too many apps

I prefer to have as less extra tokens to be used as possible. And IMO it's more clear to use sybols instead of letters, like in the UNIX style you use a minus symbol and a letter and an extra space, while in the syntax I suggested it's more clear because of the use of tokens to indicate the type of header data.

for compatibility reasons this is my edited plan:
Program:TESTSRC
.HEADER prgm
DiagnosticsOff
.and the rest of the code...

Program:HEADER
TEST "A little test prog" [8142241818244281]


It will be nice if you create a Framerate feature, what makes possible, that you can choose a  FPS value for every loop.
The prog waits at the end of the loop until the value is reached.
It will be helpful for loops, which have differently fast frames, for example by a space shooter, that would have lags by to much active objects.

I wonder if it would be feasible... it would be cool indeed, though. Personally I just:

 1: add some artificial delay that depends on the amount of objects on the screen
or
 2: simply display those objects on the screen even when unused, like a blank sprite using the OR logic.

In both cases, for tilemaps that only use one wall tile and one floor tile, never do like I did in the BASIC game Illusiat and not display any sprite for floor, because then when walking through areas with few walls, it moves many times faster than when there are many walls.

It might be ready tonight, because as another last minute decision, I decided to add support for expression valued label jumping!  The main reason is I thought it would be cool to add function pointers (which point to routines instead of data) because then you can do A LOT of crazy stuff with that.  For instance, lets say you write a subroutine that takes every element in a list and does an operation to it.  You can call that with a subroutine that takes as arguments: a list and a function pointer.  The routine then would call that function on each member of the list.  Like a function that squares the number, doubles the number, adds 1 to the number, or something really complicated.  Plus, a lot of asm programmers have been bugging me to add it for their other diabolical uses .


By the way, the new syntax for recursive subroutines is now this: sub(LBL^r,1,2,3)

Its becasue it makes it easier for the compiler to know what type of routine it is before evaluating the arguments.  Surprisingly though, you rarely need it. Tail calls don't need them so you can actually write a lot of recursive subroutines already without this new feature.  Like for instance, this:

:.RECFACT
:
:.Find 6 factorial
:Disp sub(F,6)>Dec
:Return
:
:.FACTORIAL
:Lbl F
:!If r1
:  1
:  Return
:End
:r1*sub(F,r1-1)
:Return

EDIT: @Nemo
Yeah, *2 is shift left and /2 is shift right.  They automatically optimize to the bit-shift instead of the multiplication.