i think he's actually wondering why that comparison actually works in the first place.
well this is how the program does it when running:
it starts out with this.
if variable$="bla" or variable$="bli"
it then sees if variable$ is in fact "bla." if it is, that whole comparison turns into ("evaluates as") 1.
if 1 or variable$="bli"
same thing again.
if 1 or 0
(variable$ can't be both bla and bli at the same time now can it?)
it finally performs the OR on these two numbers. 1 OR 0 = 1.
if 1
IF then checks to see if its test is 1, and it is, so the code is run.
this is boolean logic.
and come on akat, you've used DB and you never understood what OR was in IF statements? ;)
well this is how the program does it when running:
it starts out with this.
if variable$="bla" or variable$="bli"
it then sees if variable$ is in fact "bla." if it is, that whole comparison turns into ("evaluates as") 1.
if 1 or variable$="bli"
same thing again.
if 1 or 0
(variable$ can't be both bla and bli at the same time now can it?)
it finally performs the OR on these two numbers. 1 OR 0 = 1.
if 1
IF then checks to see if its test is 1, and it is, so the code is run.
this is boolean logic.
and come on akat, you've used DB and you never understood what OR was in IF statements? ;)