Most useful/needed stuff which should be added

[na_th_an]

Nothing very fancy, but drawing a whole tiled map to screen is just too slow using PRINT

Anyways, thanks for the pointers. I'll study how this fastcall scheme works now that I have that piece of code and will make my own (handling ATTRs as well). The bad news is that, unless it's included in the language default set of libraries, I won't be able to use it for the Bytemaniacos compo. :mrgreen:

Thanks again, now I'll wait patiently for the implementation of user defined types Btw, I remember having implemented type structures in our compilers project at college in a very simple fashion. You had to calculate where to read/write data by adding the "sizeof"s of all members before the one being accessed. Note that this can be always calculated in compile time, so, at the end, they are just normal variables in the compiled code. I mean, you had for example the variable coordinates which had two integer members, x and y. Once compiled, you in fact had two variables coordinates.x and coordinates.y of type integer in the generated code. That way, adding support to user defined types to our compiler didn't need us to change the expresion handling. I don't know if this makes sense, but that's what I recall from memory. We did this project 8 years ago.

I have assembly code to draw a tiled map to screen and it's somewhat fast. Maybe you are interested on it to be included as well. (As long as you all don't make fun of it again claiming it's automaticly generated code by a compiler ).