comment on

One thing that will surprise people is that it contains no provision for numeric comparison, so by the numeric/string duality, numbers will be compared as strings.

Internally, Perl knows when to implicitly convert a number to a string and vice-verse, so a new smart match should be able to know when it's dealing with numbers.

Following the proposed "RHS decides the op", then when the RHS is an actual number, it could coerce the LHS to a number.¹

Overall, I like this proposal. It is far better than loosing smart match (and, especially, given/when).

---

¹In theory it could check both sides for numbers, but I would rather let the RHS blindly impose numericy on the LHS for consistency.

In reply to Re^2: Bring back the smartmatch operator (but with sane semantics this time)! by RonW
in thread Bring back the smartmatch operator (but with sane semantics this time)! by smls

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.


The stupid question is the question not asked
	PerlMonks