08-10-2022, 11:07 AM
The ramtop here does not make much sense: you're compiling your program to *machine code*! hence your program is already over the ramtop!
This is a difficult question as, for the moment, I'm still developing a linker to deal with memory allocation. The heap space starts at the very beginning of your program along with your variables. This is done to make SAVE "" DATA to work and preserve the heap and the program state (i.e. if you want to implement the feature of saving the game and resume it later).
The ramtop is, by default 32768 (non-contended RAM). Your program starts at 32768 with a jump (JP) over the HEAP. You can generate the assembly with
Have you read this thread?
https://www.boriel.com/forum/showthread.php?tid=368 ("Using Beepola with ZX BASIC")
This is a difficult question as, for the moment, I'm still developing a linker to deal with memory allocation. The heap space starts at the very beginning of your program along with your variables. This is done to make SAVE "" DATA to work and preserve the heap and the program state (i.e. if you want to implement the feature of saving the game and resume it later).
The ramtop is, by default 32768 (non-contended RAM). Your program starts at 32768 with a jump (JP) over the HEAP. You can generate the assembly with
--asmand see the resulting ASM listing.
Have you read this thread?
https://www.boriel.com/forum/showthread.php?tid=368 ("Using Beepola with ZX BASIC")