https://github.com/geon/zpallocator/blo ... xample.asm

The idea is to be able to use the zero page for all variables. You allocate a zp address when you need it, and when you are done with it (ie. at the end of the macro/function scope), you deallocate it.



This way, I can write macros and pass arguments by reference without worrying about collisions.

I could use some help to define a couple of ranges of reserved zp addresses. I don't care about basic, so I can use $02-$70 or so without problem, but I might want to use some kernal routines like screen io and the jiffy clock. I'm not sure what other areas of the zp are important.

Not sure I understand. It looks like you're allocating at build time, right? How do you handle run time conflicts like one routine reusing the location reserved by another routine but calling each other?

André

_________________
Author of the GeckOS multitasking operating system, the usb65 stack, designer of the Micro-PET and many more 6502 content: http://6502.org/users/andre/

Yes.



For a function, you would need to allocate the address permanently. It works better with macros.

Then don't you use macros in functions?

Did you try to 'simulate' it e.g. with a paper walk through?

Writing up how it works for a few real world test cases helps a great deal in understanding if it really works or where the pitfalls are.

_________________
Author of the GeckOS multitasking operating system, the usb65 stack, designer of the Micro-PET and many more 6502 content: http://6502.org/users/andre/

Actually no. Or rather, I haven't used functions at all so far, just macros.



Yes, I do TDD. I'll have to look at functions.

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

Well done geon, thanks for sharing your creation!