I certainly don't recommend it for production use

If one really needs the behavior of a JS-like === very often this could be a way to achieve it. The old behavior of comparing only the stringified values could still be achieved by explicitly stringifying the arguments, e.g.:  "$rx" cmp "$ry".

IMHO not overloading is the problem in perl5 but the lack of alternative or freely named operators. Actually overloading results in compatibility problems.

Anyway the fact that it's "a global change of regex" really surprises me, I expected it to be reduced only to the scope of the file...

I expected it to be reduced only to the scope of the file...

There's only one Rexexp package, not one per file.

Im still confused, there is no way to reduce the effect of overloading to just the file which imports a modul with an overloaded Regexp package?

(except maybe implementing a switch to default behavior within the overloading methods)

Cheers Rolf

UPDATE: might be possible with eval 'no overload "cmp"; see Run time Overloading