![]() ![]() What exactly is the limit being reached? How would QB64 compiling itself make any difference? I'm pretty positive QB64 is not at the verge of being too large for gnucpp to compile it. I don't understand what the issue is of compiling. Sure, C has its limit, but it should be thousands of times greater and not something any current QBasic program (unless it loops infinitely) would reach. I know in QBasic, one usually gets a stack space error because a sub called itself too many times, but I don't get why that would be a problem in C . I'm looking at getting QB64 to self-compile VERY SOON to overcome these discrepancies because it's gotten to the point where I'm afraid to add anything new for fear of not being able to compile it at all!First, rpgfan3233 is right, vortex.bas also fails. Truth be told, the QB64 compiler has reached the limits of what is possible in QB7.1 (believe me I've tried ALL the tricks like multi-modular, compiler options and recoding some bits) and even though it runs in the interpreter fine I'm having major difficulties getting it to compile into a stable. "For each programmer, there is an equal and opposite programmer who can't stand to read the first programmer's code." - Snook I downloaded Demo #6, unpacked it to C:\Phylo\qb64 (such that data, internal, and samples were in that folder), then ran compile.bat and entered "samples\3dballs.bas". Xwing.bas gives me: "Out of stack space in line No line number in module MODULE2 at address 2641:0054"ģdballs.bas immediately gives "Out of stack space in line No line number in module MODULE3 at address 33D8:60E4" GalleonI was unable to compile two of the sample programs, for each of these I got an out of stack space error. ![]() If you've got a program you think SHOULD compile/run (given the limitations of mentioned in readme.txt of Demo #6) but don't know what the problem is, feel free to post a link to it and I'll do the hard work. But, if you do find (or have found) something weird now is the time to report it so I can fix it. If a bug has already been mentioned on the forum or in readme.txt of the download, you needn't repeat it here. I'm making a list of bugs/problems to fix for Demo #7. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |