So I don't know what's wrong with line 20. You cannot remove the same number that you already eliminated. My goal is to eliminate all nine numbers to win the game anything short of that will end the game. It's a long program and it always happen when I program it to eliminate the 5th number. Out of memory in 20 (I can't continue writing this program after line 6690) I'm marking a program that suppose to eliminate a number at a time, but when I run this program, it says:Ģ0 LET A=1: B=2: C=3: D=4: E=5: F=6: G=7: H=8: I=9 and enabling more storage) but for now there is still too much to do to get the GW-BASIC emulation to where I want it to be, so it will not be soon.Īs for other languages you could use, I find Python very suitable for the sort of scripting and file editing you mentioned in your earlier post, and indeed for larger projects (PC-BASIC is written in Python). I've had requests before to open up the memory limit, as indeed 64K is a bit silly on computers with 8G RAM and more, and I may well implement something in future (disabling POKE, VARPTR, etc. If your variables are whole numbers in the range, you could consider declaring ints: DIM A%(2500), which use only 2 bytes each 8*2500*2=40K should fit. If you declare them as DIM A(2500) they will be single-precision floats, which take 4 bytes each you'd need 80K which is indeed too much.
In your case, I understand you use 8 arrays of 2500 entries. Unfortunately, switching to a 64-bit computer will not make a difference. You can get a bit more memory by using the option -reserved-memory=0 but to be honest the difference isn't huge (you gain about 3K). Sadly that means a 64KiB limit on data, as GW-BASIC uses 16-bit pointers to address its variables (see e.g.
PC-BASIC tries to emulate GW-BASIC as closely as possible, which means its internal addressing and representation of variables is the same.
0 kommentar(er)
