Thanks for that.
For a decade or more I've habitually used and/or/not over &&/||/! in most situations in my code and, whilst I recall having encountered a handful or less situations where the precedence was wrong for my intent the first time I ran the code; I don't recall any occasion where it was something that I didn't discover at first run, or had any trouble locating and fixing. No latent bugs or deeply disguised issues that took any great effort to track down and fix.
My feeling, without trying to put any great store in the accuracy of that feeling, is that I've been bitten (far) more often by the high precedence versions than the low. Mostly Perl warns me about them, but one or two have taken some effort. Of course, now I should respond in kind with examples; and I've racked my brains and can't reproduce anything that is a good example. I'll come back if I rediscover any of them.
Please note, I'm not really arguing with your POV; just noting that my own experience doesn't reflect the strength of feeling you have on the subject.
In reply to Re^4: Thoughts on using and, or, and not over && || !? (a few cases)
by BrowserUk
in thread Thoughts on using and, or, and not over && || !?
by Argel
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |