I ask, because it strikes me as one of those things that would be a really bad idea. It's easy to look at //= and know, "Oh, I better be using Perl 5.10 or newer.
And I was just thinking yesterday about how perl made // and operator while in other languages it was the lead-in to a comment and how perl has no syntactic multi-line comment blocks.
But if you saw:
You would have to know that for that to work, you'd have to be in perl 5.20 or newer, as it throws an error if you try to multiple a string times an integer.' ' x $a * $b;
It's not like you have a choice. You say :
it's really hard to look at an operator and have to worry that code that uses it might break due to precedence changes between Perl versions.But the fact is you wouldn't. If you had an expression like the above, it would be broken and not work pre-pV20 (or whatever). If you are using such a construct in your current perl -- my question was how are you doing it? Could you give some examples of how you use the current behavior to produce useful code?
In reply to Re^2: Precedence design question...'x' & arith
by perl-diddler
in thread Precedence design question...'x' & arith
by perl-diddler
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |