<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Methods are immutable, BTW. When you edit one in the debugger it does a "become".<div><br><div><div>On Mar 8, 2014, at 12:52 PM, Jecel Assumpcao Jr. <<a href="mailto:jecel@merlintec.com">jecel@merlintec.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div style="background-color: #fff;">
<span style="display:none"> </span>
<div id="ygrp-text"><p>Michael,<br>
<br>
> But what about a method slot? If I edit a method in a clone, the <br>
> original is /not/ affected.<br>
<br>
This is a GUI issue, not a language one. The idea is that the most<br>
common use for editing a method in an object that also exists in other<br>
objects in the same "clone family" is that you now want it to be<br>
different. You want to start a new clone family.<br>
<br>
Note that if you edit the exact same method in a debugger instead of an<br>
outliner then your change *will* be applied to all the objects in the<br>
clone family. The idea here is that you found a bug and so all copies of<br>
the method should be changed. So these two tools act very differently<br>
but the underlying language is the same.<br>
<br>
"Read-only" means for normal use. Besides methods, we also have<br>
immutable strings (what would be Symbols in Smalltalk-80). The<br>
programming tools (and the mirror objects they are built on) are not<br>
normal use. If we didn't have this "escape hatch" it would be impossible<br>
to create these read-only objects in the first place.<br>
<br>
-- Jecel<br>
<br>
</p>
</div>
</div>
<!-- end group email -->
</blockquote></div><br></div></body></html>