QBasic 1.1 bombs-out

[Guest_imported]

Hello All,

I'm a long-time QBasic user, and have bumped into a re-occurring problem : At one time of another, when I have just added something to my program, QBasic does not want to run my program anymore, generating argument mismatch errors on places that worked fine a minute ago, and that are not related in any way to the changes I just made.

To make it all even more funny, when I remove the sub/function declarations, at the start of my program, my program functions o.k. again. That is, up untill the point where QBasic inserts those lines again (due to saving the program).

So, I'm quite sure it's not a problem of my program, but some sort of bug (?) of QBasic.

My question : 1) Does anyone know of it, 2) does anyone know how to solve the problem (update perhaps ?), 2) if solution is present, how can i find when this problem (why) it's going to happen.

BitFiddler

 

[BitFiddler]

@MiggyD
First off, due to a pourly done snipping of mine, the command DEFINT A-Z became part of a remark-line :-( It should be present just above the "Call ViewMap" -line.

And, as far as I can tell, Constants do not have a fixed type (integer,long,string, etc). A constant can hold *any* type of number, as well as strings (without having to add a '$' -char to the constant-name, mind you)

> "They even appear/dis-appear when adding/removing a simple constant-declaration." This is (as far as I can see) not due to a 'headache' as you name it (why should an argument-type mismatch on an totally unrelated variable disappear when removing an constant-declaration ?), but the result of a simple,unchecked (internal) buffer-overflow.

Furthermore, if the above mentioned constant-declaration would cause the headache, I would have needed to remove them all, not just one to get the program to work again ...

By the way, If you wantI can send you my version of QBasic, together with the above program, so you can see the error for yourself, and eventually tinker around with it ...