Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site unc.unc.UUCP
Path: utzoo!linus!decvax!mcnc!unc!rentsch
From: rentsch@unc.UUCP (Tim Rentsch)
Newsgroups: net.lang.st80
Subject: Re: at:put: not doing what is expected
Message-ID: <1036@unc.unc.UUCP>
Date: Fri, 21-Feb-86 01:16:00 EST
Article-I.D.: unc.1036
Posted: Fri Feb 21 01:16:00 1986
Date-Received: Mon, 24-Feb-86 05:38:00 EST
References: <1@randvax.UUCP> <975@unc.unc.UUCP> <21930@apple.UUCP>
Reply-To: rentsch@unc.UUCP (Tim Rentsch)
Distribution: net
Organization: CS Dept, U. of N. Carolina, Chapel Hill
Lines: 19
Summary: 

In article <21930@apple.UUCP> mark@apple.UUCP (Mark Lentczner) writes:

>  It is true of all message sends that have special byte codes that the
>  interpreter will execute some compilied version of the code no matter
>  what you write in the methods.  As to whether you can override the
>  behavior in subclasses or not depends on both the message involved
>  and the interpreter.  

Yes, but....  which ones do or don't is part of the specification of
the virtual machine ("No lookup"), and, if I'm not mistaken, at:put:
in class Array is not one of those.  In any case, the at:put: which
was not looked up was in a *subclass* of Array.

Mark's point about == and proxy objects was interesting.  This argues
for really *everything* being sent as a message.

cheers,

Tim Rentsch