<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 20 Nov 2018, at 01:16, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com" class="">eliot.miranda@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi David,<br class=""><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Mon, Nov 19, 2018 at 9:52 AM David T. Lewis <<a href="mailto:lewis@mail.msen.com" target="_blank" class="">lewis@mail.msen.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, Nov 19, 2018 at 09:32:17AM -0800, Eliot Miranda wrote:<br class="">
> Hi All,<br class="">
> <br class="">
> In VisualWorks Message implements #= & #hash naturally; two messages<br class="">
> whose selectors and arguments are #= are also equal. But in Cuis, Squeak<br class="">
> and Pharo Message inherits #= and #hash from Object, i.e. uses identity<br class="">
> comparison. This is, to say the least, annoying. Any objections to<br class="">
> implementing comparing in Message to match VisualWorks?<br class="">
> <br class="">
<br class="">
That sounds like an obviously good thing to do :-)<br class="">
<br class="">
Is the lookupClass instance variable relevant for comparisons? I am<br class="">
guessing not, since we already have #analogousCodeTo: for that type of<br class="">
comparison.<br class=""></blockquote><div class=""><br class=""></div><div class="">For me it is relevant. Two messages with different lookupClasses, e.g. one with nil and one with a specific class, represent different messages, one a normal send one a super send. So my changes in waiting include lookupClass in both hash and =. I don't think it makes much difference, but the incompatibility with VisualWorks, while regrettable, feels correct to me.</div><div class=""><br class=""></div></div></div></div></blockquote><br class=""></div><div>To me this looks like a good change, yes.</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Marcus</div><br class=""></body></html>