possible to pass a function to a macro? or find the identifier for the current function? about millfork HOT 3 CLOSED

There is currently no way to make it cleaner, but you found a really nice place for potential improvements, thanks!

So there are two potentials for improvement here:

• functions are not "typed things", which is the internal Millfork term for variables, constants and similar things – functions are merely "things" – and right now, macro parameters have to be "typed things", even if we don't care about their types

• macros should preferably know the function and segment they're in – and even normal functions should be able to refer to themselves without repeating their name

I'll figure out some improvements here, they should land in the next release.

BTW, A2600 support in Millfork was more of an afterthought, in the lines of "it'll compile, so why not". It's surprising, but nice to hear that it turned out to be practical.

from millfork.

Thanks! It'll be a help. I did notice the VCS support was minimalist, and wrote my own platform file and includes. But MFK seems pretty general purpose and can fit into many of the VCS bankswitching arrangements. And MFK is very fast... I've only needed to write about a dozen lines of the graphics kernel core loop in ASM. Otherwise pure MFK.

It is limited to the 128 B of RAM for regular variables. VCS cartridges use a complicated system for cartridge RAM, where separate addresses are used for read/write (and RMW ops like inc/dec don't work). I've had luck wrapping that in a few macros and using pointers. With care it compiles to code very similar to what I would write in assembly. :) I'll try to document some of it when I have time.

from millfork.

I think that the problems have been solved adequately in 0.3.30.

from millfork.