Some languages force evaluation of the second term to ensure consistency of any side-effect behaviour. - Kemp
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Charles Sent: July 1, 2002 11:52 PM To: [EMAIL PROTECTED] Subject: [REBOL] Evaluating if's Here's a little question. Perhaps I've been spoiled in other languages, but this is starting to frustrate me. I have something like: if THIS and THAT [] Thing is, if THIS is false, it continues to evaluate THAT anyways. What's the point? The result is obviously false anyways. I'm working on a case like this (perhaps someone can provide a more elegant solution): if (2 = length? p: parse filename ".") AND (not none? find pick p 2 "htm") [ ... Obviously, if the first condition is false, I want it to quit without evaluating the second condition. Help? Any way I can continue doing this in the same line, and without worrying about throwing and catching errors? Or am I more or less doomed to yet another nested if? Thanks folks. --Charles -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes. -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
