Re: Messages as first class objects
From: Isaac Gouy (igouy_at_yahoo.com)
Date: 05/02/04
- Next message: Daniel T.: "Re: composition vs. inheritance"
- Previous message: Isaac Gouy: "Re: Messages as first class objects"
- Maybe in reply to: Guy: "Re: Messages as first class objects"
- Next in thread: Cristiano Sadun: "Re: Messages as first class objects"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 2 May 2004 12:01:03 -0700
"Volker Bäcker" <baecker@crbm.cnrs-mop.fr> wrote in message news:<c6tons$gbfmc$1@ID-218123.news.uni-berlin.de>...
> "Calum" <calum.bulk@ntlworld.com> schrieb im Newsbeitrag
> news:c6tf7c$2g0$1@newsg1.svr.pol.co.uk...
> > I have read that "messages", "member functions" and "methods" are all
> > fairly similar concepts. For example
> >
> > io.write("Hello")
> >
> write("Hello") is a message that is sent to io. io has (hopefully) a member
> function write. This member function is a method.
> > is fairly unambiguous. But how many languages allow you to take a
> > message in isolation? e.g.
> >
> > x = write("Hello") # x is a message
> > io.x # send message x to io
> Smalltalk does. In VisualWorks Smalltalk there are classes like
> CompiledMethod and others that represent methods.
Are we talking about 'messages' or 'methods'?
Here's a Smalltalk 'message' example:
messageSelector := #write:.
io perform: messageSelector with: 'Hello'.
- Next message: Daniel T.: "Re: composition vs. inheritance"
- Previous message: Isaac Gouy: "Re: Messages as first class objects"
- Maybe in reply to: Guy: "Re: Messages as first class objects"
- Next in thread: Cristiano Sadun: "Re: Messages as first class objects"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|