<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
Hi Chris,<div><br></div><div>I think we mean the same here. I just wanted to add the word "meaningful" to your suggestions:</div><div><br></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px;line-height: 19.5px"> "Answer whether the receiver can be sent a message named aSymbol and expect a meaningful answer."</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px;line-height: 19.5px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px;line-height: 19.5px">Best,</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px;line-height: 19.5px">Marcel</span></div><div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 06.08.2019 22:05:35 schrieb Chris Muller <asqueaker@gmail.com>:</p><div style="font-family:Arial,Helvetica,sans-serif">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Aug 6, 2019 at 3:18 AM Marcel Taeumel <<a href="mailto:marcel.taeumel@hpi.de" target="_blank">marcel.taeumel@hpi.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div id="m_1082518092873313275gmail-m_-392015641575316695__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: rgb(0,0,0)">
One can always send any message to any receiver. :-)</div></blockquote><div><br></div><div>Sure, a Smalltalk developer gets that. But from the context of what's meaningful to a Dynabook user simply interested in using Squeak objects as an app, they simply know they don't want to see that "does not understand" error message. "Can send" is synonymous enough with that. But my main point is not about what exact words, but about the idea of speaking to that specific audience through the #firstComment.<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div id="m_1082518092873313275gmail-m_-392015641575316695__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: rgb(0,0,0)"><div><br></div><div>The question is whether the answer can be meaningful or not. Can a client expect a meaningful answer from such a message send? </div></div></blockquote><div><br></div><div>Right. The thrust of my post is that the "client" in your statement above is a Dynabook user, and _not_ a Smalltalk developer.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div id="m_1082518092873313275gmail-m_-392015641575316695__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: rgb(0,0,0)"><div>Neither mentioning method dictionary nor superclasses help figure out when and why to send #respondsTo: to an object. Only Behavior is the domain and place to talk about method dictionary and superclasses. The comment in #canUnderstand: does already mention method dictionary and superclasses.</div></div></blockquote><div><br></div><div>Users are only concerned with "sending messages to objects", nothing else. Those Dictionary's are below the level of what they care about. Even the notion of inheritance (superclasses) will cause their eyes to glaze over. Sending messages to concrete instances is where the rubber meets the road. The #firstComment is a opportunity to open up the Squeak class-library to a new group of people, without affecting our ability to talk to Smalltalk developers in the 2nd - nth comments. But most of the time, I'm sure the one single user-centric comment is sufficient for both groups.</div><div><br></div><div> - Chris</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div id="m_1082518092873313275gmail-m_-392015641575316695__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: rgb(0,0,0)"><div><div><br></div><div>Just my two cents. :-)</div><div><br></div><div>Best,</div><div>Marcel</div><div class="m_1082518092873313275gmail-m_-392015641575316695mb_sig"></div>
</div><blockquote class="m_1082518092873313275gmail-m_-392015641575316695history_container" type="cite" style="border-left-style:solid;border-width:1px;margin-top:20px;margin-left:0px;padding-left:10px;min-width:500px">
<p style="color:rgb(170,170,170);margin-top:10px">Am 06.08.2019 07:00:19 schrieb Chris Muller <<a href="mailto:asqueaker@gmail.com" target="_blank">asqueaker@gmail.com</a>>:</p><div style="font-family:Arial,Helvetica,sans-serif">
<div dir="ltr">Hi there, as we go to fix comments, may we take the opportunity to see if we'd like to change the nature of the comment in general?<div><br></div><div>Here's where I'm going: "built-in documentation". For all #firstComments anyway, in methods throughout the system, if we would direct those particular comments toward the *Dynabook user*, something like:</div><div><br></div><div> "Answer whether the receiver can be sent a message named aSymbol."</div><div><br></div><div>then relatively simple systems can easily extract it to help connect users to a Dynabook experience. Separate comments can be used to describe the 'dictionarys' or whatever implementation if desired, but since they wouldn't be the #firstComment, they wouldn't be presented in the user layer.<br></div><div><br></div><div>It's a simple but powerful leverage, what do you think?</div><div><br></div><div>Best,</div><div> Chris</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Aug 5, 2019 at 9:39 AM <<a href="mailto:commits@source.squeak.org" target="_blank">commits@source.squeak.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;min-width:500px">A new version of Kernel was added to project The Inbox:<br>
<a href="http://source.squeak.org/inbox/Kernel-cmfcmf.1251.mcz" rel="noreferrer" target="_blank">http://source.squeak.org/inbox/Kernel-cmfcmf.1251.mcz</a><br>
<br>
==================== Summary ====================<br>
<br>
Name: Kernel-cmfcmf.1251<br>
Author: cmfcmf<br>
Time: 5 August 2019, 4:39:08.95825 pm<br>
UUID: eb7ae4e2-7697-7745-b4c3-4f9ce5975e2b<br>
Ancestors: Kernel-mt.1250<br>
<br>
Clarify comment in Object>>respondsTo: to indicate that the method can also be defined in a superclass.<br>
<br>
=============== Diff against Kernel-mt.1250 ===============<br>
<br>
Item was changed:<br>
----- Method: Object>>respondsTo: (in category 'class membership') -----<br>
+ respondsTo: aSymbol<br>
+ "Answer whether the method dictionary of the receiver's class or any of its superclasses contains <br>
- respondsTo: aSymbol <br>
- "Answer whether the method dictionary of the receiver's class contains <br>
aSymbol as a message selector."<br>
<br>
^self class canUnderstand: aSymbol!<br>
<br>
<br>
</blockquote></div>
</div></blockquote></div><br>
</blockquote></div></div>
</div></blockquote>
</div></body>