> Then, we could simply write our own versions of shortcutting AND and OR.
> The difference would be that it would look like a function, not like an
> operator. Compare:
>
> expr1 && expr2
> vs.
> AND(expr1, expr2)
>
> but at least, there would be no confusion WRT precedence rules.
And people, seeing every other operator overloaded for a particular
module, will assume that || and && do the right thing too.
But they won't :-(
This is a real world problem. I have three separate modules -- Switch,
Quantum::Superpositions, and Lingua::tlhIngan::pIqaD -- that don't DWIM
because I can't overload || and && to work correctly.
Damian
