|Think about Loose Coupling|
Re^5: Looking for discussions of "block after or" syntax errorby Laurent_R (Abbot)
|on May 01, 2013 at 22:31 UTC||Need Help??|
Well, you are not "knowing" you are "guessing"... ... and that's not a good base for designing code.
This is unfair, Rolf. I am certainly not claiming to be an expert on the subject, this is why I am saying I may be wrong. But, please, don't say that I am just guessing, I have done a quite a little bit more work than just guessing. I am just admitting that I might be completely wrong, if such is the case, please show me why, and I will be happy to recognize it.
What's worse, I also guessed that and and or have the same precedence ...
Well, I knew they did not have the same precedence. But my point is that this is probably essentially irrelevant.
... but now take a look what B::Deparse says: ...
$a and $b or $c
What I am saying: true, i.e. $a and $b, if they are both true, otherwise, $c. Exactly equivalent to $c unless $a and $b;
$a or $b and $c
True if $a is true. Otherwise, true only if $b and $c are both true. Again, it seems to me that this is exactly equivalent to $b and $c unless $a;
In brief, the two deparse examples that you have shown confirm exactly and precisely by left-to-right Boolean interpretation with short-circuit that I made.
Again, I am being very careful on this, I may be completely wrong. But, *please*, don't use this uncertainty to claim that I am just guessing.