comment on

Well as I already said

I certainly don't recommend it for production use

, a simple comparison function is much easier to maintain. But Beth asked for options with overloading, and thats the answer.

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...

Cheers Rolf

In reply to Re^3: What is the best way to compare variables so that different types are non-equal? (overloading "cmp") by LanX
in thread What is the best way to compare variables so that different types are non-equal? by ELISHEVA

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Just another Perl shrine
	PerlMonks