ABasiC program size
10 messages in this thread
HELP! I'm getting "PROGRAM TOO LARGE" on the ABasiC program which I've
invested 3 weeks in and which is about 60% done. I can't find any info in
the manual as to the max allowed program size. I naively assumed as long as
I was showing 179k free even after initializing arrays that I was ok. My
source code (as determined by fre before and immediately after loading ) is
about 60,100 bytes. Does anyone know is this a real limit? Or is it another
bug. After adding the lines which give me the "Program Too Large" message,
the lines appear to still be there in the source, but I get "Syntax Error" in
random older lines when I try to run. Any advice greatly appreciated. My
machine is 512 k. Since I've been writing program modules more or less in
random order I'm definitely not at a good point to CHAIN the "second half" of
the program. Dick Darling
Enter command, N for next
message or <CR> for menu : n
Just a guess, but I've had the same problem. The screen depth eats up ALOT of
memory. Try lowering it and see if it runs.
Enter command, N for next
message or <CR> for menu : n
An interesting suggestion, and it's true that the screen depth really soaks
up memory (and slows the program), but I get my "Too Large" message when I'm
still in edit mode. I don't believe the editor is smart enough to parse the
entire program and decide I've exceeded some run-time limit. But maybe…
Actually, I've done some checking since I left that last mess- age and found
that I CAN merge two program pieces and obtain a combined program larger than
the editor will accept as a single unit. Don't ask me why. Dick Darling
If your using ED , you can use the SIZE option to increase the file size limit.
Any help?
Yeah, I HAVE to increase the SIZE option when I use ED because of the program
length. But ED isn't where I have trouble. It's when I LOAD the file into
ABasiC that I get the error msg. A new development: I've found that I can get
the "Program Too Large" even after deleting fairly large chunks of the
program (15%) if I exceed some fuzzy limit on the NUMBER OF VARIABLES. I'm
really not using very many, but I can sometimes eliminate the error condition
just by reusing an old name instead of creating a new one.
The answer is…. vectorize? After all, the Amiga uses lists as a library
primitive — maybe the makers of ABasiC just assumed that everyone would
program in that sort of style.
I'm afraid you're beyond me. Can you
elaborate?
Dick Darling
Sorry I'm no help, and I think I'll wait for MSBASIC or C to be available
before I get serious about programming this thing. (Available means to us
common folk in Michigan, can't get anything here yet)
what side of mich, i'm in Grand Rabbits.
sdp
That's probably wise. From what I hear even the current release of C is
buggy. This is what we get for jumping in this early. And I think CBM may
have released just a tad early, too. Dick Darling