I received this report of an 'LBB bug': "this program Works in Liberty BASIC but fails under LBB. The error message is: Bad hex or binary at line 17". Here is line 17 of the program in question:
Code:AW.ACTIVATE = HexDec("&20000")
It's perfectly true that this statement is accepted by LB but reports the above error message in LBB. But is the conclusion that it's an LBB bug reasonable?
Let's try this code in Liberty BASIC 4.04:
Code:AW.ACTIVATE = HexDec("&20000")
print AW.ACTIVATE
The value printed is.... zero!!
So in fact what we have is a mistake in the OP's code (he meant to write &H20000) which was correctly reported by LBB but incorrectly ignored by LB 4.04 - and the wrong value returned!
The moral of the story is: don't automatically assume that, if LBB reports an error but LB doesn't, LBB is at fault.
Richard.
Logged