Re: re: Applesoft IF...THEN BUG

[edward@pro-ren.cts.com (Edward Floden)]

WULF@cip.physik.uni-stuttgart.de (Wulf Hofbauer) writes:

>>         IF B THEN GOTO 100
>>         IF B THEN 100
>>         IF B GOTO 100
>> 
>> The manual says that all of these statements have a valid syntax. But when
>> I try "IF B GOTO 100" (and yes, there really is a line 100 somewhere), I
>> get an undefined statement error! Replacing the GOTO with THEN or THEN GOTO
>> will allow a successful run.
>
>I guess all of these should do (though probably noone would use the last
>version). The Applesoft interpreter is FULL of bugs (after all, it's from
>Microsoft...), but in this case I'd rather tip at a problem of BASIC.SYSTEM
>(though I can't confirm it positively).

Now for the weird part: this only happens on one machine, a IIgs that I use
at work. Neither of the GSes at home have a problem; only the work CPU
exhibits this behavior.

I suspected that BASIC.System was corrupted, and placed a new copy on the
hard drive, but not without first saving the old version. I compared the old
and new files; but they're identical, with not a single byte of difference.

My guess at the moment: RAM got hosed, maybe just a single bit, and the copy
of BASIC.System in memory was the unlucky resident of that RAM location. Now
all I need to do is reproduce this problem. :)