I just went through and replaced all my:
<loop structure>
IF condition THEN
block of code
END IF
<end loop structure>
with:
<loop structure>
IF <NOT> condition THEN _CONTINUE
block of code
<end loop structure>
It shaved off over a couple dozen END IFs in my ap without changing the action. It just requires an opposite condition test.
Doesn't really reduce typing, but cleans up some indentation nesting, which I did find desirable. Leaves a bit more space for comments.
Only thing to remember:
IF NOT (condition) THEN _CONTINUE.... may not be the same as IF (condition) THEN...(code stuff)
For example:
IF x AND y THEN
do stuff
END IF
Now, if x = 4, and y = 2, then x AND y = 2, so you DO STUFF.
Now let’s try the other.
IF NOT (x AND y) THEN _CONTINUE
do stuff...
In this case, (x AND y) end up evaluating to 2, same as above, so NOT 2 gives us -3. -3 is still regarded as a TRUE evaluation, so you now _CONTINUE and skip doing your stuff.
The *ONLY* time you can safely interchange the two methods, is when you’re dealing with binary results. (0 and -1 only)