04-13-2011, 01:44 PM
The heap should be user locateble in either high or low memory.
For background go to:
<!-- l --><a class="postlink-local" href="http://www.boriel.com/forum/bug-reports/paper-border-rerun-bug-t626.html#p2244">bug-reports/paper-border-rerun-bug-t626.html#p2244</a><!-- l -->
If I had a game in two parts like a multiloader game and the game parts of
it go into high memory then it is quite possible that it would wipe out
the heap and the shared data there. Also you could specify heap location
manually. This is easier than POKEing and PEEKing but not as easy as
sharing the variables themselves and I think it is a good comprimize both
in terms of user ease and compiler writing and runtime size. What does waste
memory is having two runtimes in memory and the same time for a two part
program, multilevel or not. This also ensures what part of the program really
got control for example if you got to return to BASIC to load a multilevel disk
based game then the BASIC part has got the real control.
My two cents.
For background go to:
<!-- l --><a class="postlink-local" href="http://www.boriel.com/forum/bug-reports/paper-border-rerun-bug-t626.html#p2244">bug-reports/paper-border-rerun-bug-t626.html#p2244</a><!-- l -->
If I had a game in two parts like a multiloader game and the game parts of
it go into high memory then it is quite possible that it would wipe out
the heap and the shared data there. Also you could specify heap location
manually. This is easier than POKEing and PEEKing but not as easy as
sharing the variables themselves and I think it is a good comprimize both
in terms of user ease and compiler writing and runtime size. What does waste
memory is having two runtimes in memory and the same time for a two part
program, multilevel or not. This also ensures what part of the program really
got control for example if you got to return to BASIC to load a multilevel disk
based game then the BASIC part has got the real control.
My two cents.