I believe if you change that to or, you will throw an error. Or at least you should! Thinking about this, it may be simpler to think of AND comparisons a single expressions and OR comparisons as delimiting multiple expressions. In a SINGLE LOGICAL EXPRESSION evaluation will terminate when a false is encountered. If you think of what comes after OR as a NEW LOGICAL EXPRESSION it all makes perfect sense. To my twisted brain anyway.
Bob On Jan 29, 2013, at 10:45 AM, Peter M. Brigham wrote: > One situation when the order of evaluation is important is if you have > conditions that limit the scope of a general handler, eg: > > if "field" is in the target and the locktext of the target = true then… _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
