04-25-2012, 10:09 AM
I've been giving thought to this sort of issue for a while now - within the current constraints, and lacking object orientation, sprites are quite tough to do. I considered building an interface from subroutines and functions, such that you could call one and it would deal with the sprite for you - but the biggest issue is the local/global variable one - it would need arrays of data to keep track of sprites (or at least pointers) - and that would need to be global between the different subroutines. Tricky to program that /inside/ a sub 
All told, I rapidly realised it would become a messy thing to bolt on.
We do have memory allocation and de-allocation, and of course, when you ask for bytes from the pool, you get back an address. Most people would say that's a pointer, I think. The question is, how do we handle that as a general case?
All told, I rapidly realised it would become a messy thing to bolt on.
We do have memory allocation and de-allocation, and of course, when you ask for bytes from the pool, you get back an address. Most people would say that's a pointer, I think. The question is, how do we handle that as a general case?