Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!europa.chnt.gtegsc.com!news.sprintlink.net!noc.netcom.net!netcomsv!uu3news.netcom.com!netcomsv!uucp3.netcom.com!slcgate!servio!servio!aland
From: aland@servio.slc.com (Alan Darlington)
Subject: Re: Smalltalk terminology - Object, Class, and Instance
Message-ID: <1995Jun28.205511.7356@slc.com>
Sender: news@slc.com (USENET News)
Nntp-Posting-Host: servio
Organization: GemStone Systems, Inc., Beaverton OR, USA
References: <altinbayDAu4qq.LpF@netcom.com> <NEWTNews.804276785.29293.sellers@sellers.sellers.com> <Jan.Bytesmiths-2706951943380001@138.120.62.112>
Date: Wed, 28 Jun 1995 20:55:11 GMT
Lines: 21

Jan.Bytesmiths@acm.org writes:
> In article <NEWTNews.804276785.29293.sellers@sellers.sellers.com>, John
> Sellers <sellers@sellers.com> wrote:
> 
> >...actually ALMOST everything is an object.  In most 
> > implementations, messages are not objects...
> 
> Then what is the argument to #doesNotUnderstand:? An instance of Message,
> perhaps?
> 
> This may only be true of VisualWorks, in which case, the rest of the world
> screwed up!

No - Visual Smalltalk also has this.  I believe that the interpreter
packages up the selector and arguements (taken from the stack) in a
new instance of Message just before calling #doesNotUnderstand:, so
Messages are not used during normal message sends.

  Alan
  (standard disclaimers)

