So, this was unexpected behaviour? Certainly the way that Bert describes appears to be what happened in my workspace-based tests.<br><br><div><span class="gmail_quote">On 7/3/08, <b class="gmail_sendername">Bert Freudenberg</b> &lt;<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>&gt; wrote:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
Am 03.07.2008 um 05:27 schrieb Randal L. Schwartz:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

&quot;Marcin&quot; == Marcin Tustin &lt;<a href="mailto:mm3@zepler.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">mm3@zepler.net</a>&gt; writes:<br>
</blockquote></blockquote></blockquote></blockquote></blockquote>
<br>
Marcin&gt; I recently came across a piece of behaviour which is (sort of)<br>
Marcin&gt; understandable, but I wonder if it is how it is supposed to happen or<br>
Marcin&gt; not. I was running through the potsdam seaside tutorial, and I change<br>
Marcin&gt; the superclass of one of the objects from Object to WAComponent, and<br>
Marcin&gt; accepted the change. All the browser tools treated the class as if its<br>
Marcin&gt; protocol included the messages of WAComponent, but running code that<br>
Marcin&gt; sent WAComponent messages signaled MessageNotUnderstood.<br>
<br>
Are you sure you weren&#39;t dealing with a previous instance of your old class?<br>
I think this kind of a change forks the class def so that new instances have<br>
the new superclass, but old instances still have the old class and old<br>
superclass (anObsoleteYourClassnameHere).<br>
<br>
I could be wrong, but tI think that&#39;s how it works.<br>
</blockquote>
<br>
<br>
Smalltalk does not work that way. If the class format changed, all existing instance are bulk-migrated to the new class (by creating new instances and doing a forward-become on all of them).<br>
<br>
- Bert -<br>
<br>
<br>
_______________________________________________<br>
Beginners mailing list<br>
<a href="mailto:Beginners@lists.squeakfoundation.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Beginners@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/beginners" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.squeakfoundation.org/mailman/listinfo/beginners</a><br>
</blockquote></div><br>