Hi, I was hyped about the fact that much of the ZP is actually empty and not used by the system. I found this allways a huge limitation of C64 that actually most of it is occupied by the System and Basic and you could barely find 10 bytes unused.
Now in the progress of the project I can see first signs of getting it filled by the system again (now bytes $00-$21 are in use).
Of the 126 bytes, that were available before, are now only 93 left. This is not to bad still, but shows a tendancy.
Can you please consider to make it a design goal to have as much as free space in the precious ZP?
ZP is becoming in the enhanced instruction set of 65c02 even more precious, so I would love to be able to use it.
One way to achieve it would be a way to easily save and reload the parts that users might not need (e.g. Basic).
Yes I know you can work in a "don't care" mode and simply assume that the user need to reset after using your program. However that is in no way a modern approach and I like to leave a clean environment. So if you run my program from basic, I like to return to basic and find it intact (no hidden time bombs left, because something overwritten).
Also calling the basic initialize routing might not be the best, as it also clears the basic memory (overwrites what was in there in terms of sys calls or whatever).
What I am asking for is: Either reserve some of the really precious ZP space for us programmers, or create a basic/kernal routine to restore the space without deleting any other part of the ram.
Last point of consideration: Of cause If I write into areas used by basic, those data will be gone after calling basic initialize, but the basic ram should not be overwritten. I can then put temporary data into the memory section in questions and that keeps my program intact to get rerun.
Hi, I was hyped about the fact that much of the ZP is actually empty and not used by the system. I found this allways a huge limitation of C64 that actually most of it is occupied by the System and Basic and you could barely find 10 bytes unused.
Now in the progress of the project I can see first signs of getting it filled by the system again (now bytes $00-$21 are in use).
Of the 126 bytes, that were available before, are now only 93 left. This is not to bad still, but shows a tendancy.
Can you please consider to make it a design goal to have as much as free space in the precious ZP?
ZP is becoming in the enhanced instruction set of 65c02 even more precious, so I would love to be able to use it.
One way to achieve it would be a way to easily save and reload the parts that users might not need (e.g. Basic).
Edited by SerErrisYes I know you can work in a "don't care" mode and simply assume that the user need to reset after using your program. However that is in no way a modern approach and I like to leave a clean environment. So if you run my program from basic, I like to return to basic and find it intact (no hidden time bombs left, because something overwritten).
Also calling the basic initialize routing might not be the best, as it also clears the basic memory (overwrites what was in there in terms of sys calls or whatever).
What I am asking for is: Either reserve some of the really precious ZP space for us programmers, or create a basic/kernal routine to restore the space without deleting any other part of the ram.
Last point of consideration: Of cause If I write into areas used by basic, those data will be gone after calling basic initialize, but the basic ram should not be overwritten. I can then put temporary data into the memory section in questions and that keeps my program intact to get rerun.
Share this post
Link to post
Share on other sites