>You seem not to understand why LTR was invented in the first place. It was designed as a speed optimization in the days when computers were slow and expensive. To this day, that's its reason to exist. If you want to continue to use a side-effect of that optimization for flow control in your programs, do so at your own risk.
LTR is not
only for speed optimization. It can also help you avoid errors, while making code shorter.
Here is a typical VFP construct:
if type("SomeVariable") = "L" and SomeVariable
...
endif
The possible error in this case is: SomeVariable doesn't exist, or has the wrong type. (If you think this is unlikely in your code, replace with some other condition that would cause an error.)
Note that since VFP evaluates from LTR, the part after the AND will not be evaluated if the variable doesn't exist.
Of course, this is completely equivalent to:
if type("SomeVariable") = "L"
if SomeVariable
...
endif
endif
but I personally like the shorter version, and I think LTR can be trusted in this case.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)