fine tuning

[badkarma]

If PortraitIsOn = True AND LandscapeIsOn = True
ScreenIs320Square = True
A=1
End If

The above gives a compile error about then end sub ...

...but should it grumble instead about the lack of a "Then" statement on the end of the first line instead?

Also, take a look at the AND keyword ... B4P seems to uppercase this ... should it be 'And'?

[agraham]

Originally Posted by badkarma

...but should it grumble instead about the lack of a "Then" statement on the end of the first line instead?

In general for compilers the order in which errors are reported will depend upon how the code is parsed. Most compilers will not bomb out at the first error but will try to carry on compiling to show any further errors ignoring some code in the process. This means that some errors may be "hidden" until other errors are corrected. In this case it seems the lack of "End If" is stopping the compiler seeing the "If .. End If" structure so it doesn't look inside it to try to understand that.

Also, take a look at the AND keyword ... B4P seems to uppercase this ... should it be 'And'?

It doesn't really matter as B4ppc is case-insensitive but a long standing convention in Basic has been to upper-case operators like AND, OR and XOR to distinguish them from variables which are usually written with at least some lower-case characters.

[badkarma]

Excellent answer, that clears that up then.

I've often wondered about that recently about trying to compile then it gives an error "lower down" the code, then when I fix that particular error, it errors "higher up" the code....

Thanks for the explanation and education, I now know more on how things tick B4P wise. - Especially also the bit operator OR as opposed "this = x or that = y"

Cheers

Steve