Don't call an important func as part of an OR test

BlitzMax Forums/BlitzMax Programming/Don't call an important func as part of an OR test

The forum is locked. These are the original blitzbasic.com forums, kept so they can still be read. No new topics, replies or edits can be made here. To join in, head over to the Blitz3D+ forums.

Brucey
 #1
It makes sense that if the first part of the statement is true, there's absolutely no point going any further.

Does the second part of the Or make it *even truer* if the first part is true?

:-p