I am splitting hairs with this, but my nerd light turned on my head so I couldn't help myself. The result of what you described is absolutely right, and I'd say it's important to always use parentheses to ensure the order of operations is exactly as intended. I'm purely responding because it's interesting and this has caused me to learn something.
😃I don't think Blue Prism's expression syntax uses short circuit, since there's no support for AndAlso. Of course, I'm making the assumption that Blue Prism's Expression Syntax is directly based on VB.NET rather than it being abstracted/overridden with a different implementation. In Michal's example, I believe it's the operator precedence (which you mentioned) that causes his expression to evaluate to False.
In Blue Prism expressions, it would seem that this:
1=2 AND 1=1 OR 2=2
is equal to this:
(1=2) AND (1=1 OR 2=2)
Because AND has higher precedence (which of course I know you pointed out, so nothing new here), we can flip it around, and these expressions also evaluate to False:
1=1 OR 2=2 AND 1=2
(1=1 OR 2=2) AND (1=2)
And I think this is a good example that results in True showing that AND takes precedence:
1=1 OR 1=2 AND 2=2
If OR and AND were equal in precedence then this expression would result in True but instead it results in False:
1=1 OR 1=2 AND 2=3
But the only way to get True on that is to force the order of operations:
(1=1) OR (1=2 AND 2=3)
------------------------------
Dave Morris
Cano Ai
Atlanta, GA
------------------------------
Dave Morris
3Ci at Southern Company
Atlanta, GA
