07-03-2012, 06:38 PM
Hmm.
I think that's too specific - and has issues of overrun. I could have one routine at a low address that's too long, and a second routine at a higher address that then backs down and overwrites the lower one. That would be hell to diagnose!
I'm fairly Okay with zxb managing the very specific bits of memory - I just want to say "this bit goes in this zone" - and the compiler to tell me if it gets too big to fit in there...
What did you think about my bank directive idea earlier in this thread? Doesn't have to be 128K yet to start on that path. Could just cover three 48K bank areas.
I think that's too specific - and has issues of overrun. I could have one routine at a low address that's too long, and a second routine at a higher address that then backs down and overwrites the lower one. That would be hell to diagnose!
I'm fairly Okay with zxb managing the very specific bits of memory - I just want to say "this bit goes in this zone" - and the compiler to tell me if it gets too big to fit in there...
What did you think about my bank directive idea earlier in this thread? Doesn't have to be 128K yet to start on that path. Could just cover three 48K bank areas.