User Tools

Site Tools


Sidebar

Jump to
AmbientTalk
CRIME
iScheme

at:tutorial:objects

This is an old revision of the document!


In this section, we explain how the object-oriented programming paradigm is implemented in AmbientTalk.

Objects, fields and methods

In AmbientTalk, objects are not instantiated from classes. Rather, they are either created ex-nihilo or by cloning and adapting existing objects, like prototypes in the SELF programming language. The definition of such a prototypical object contains a number of fields and methods that represent the object's state and behaviour respectively.

The following code illustrates the ex-nihilo creation of an object:

> def Point := object: { 
    def x := 0;
    def y := 0;
    def init(xCoord,yCoord) {
      x := xCoord;
      y := yCoord;
    };
    def sumOfSquares() { x*x + y*y };
  }
>><object:439658>

As all definitions in AmbientTalk, objects are defined using the def keyword. In the example above, the state of the Point object is composed of x and y fields and its behaviour corresponds to the init and sumOfSquares methods. This object can be instantiated to create new points as follows:

> def aPoint := Point.new(2,3)
>><object:13393187>

Every object understands the message new, which creates a clone (a shallow copy) of the receiver object and initializes the clone by invoking its init method with the arguments that were passed to new (xCoord and yCoord in the example of the Point object). Hence, the init method plays the role of “constructor” for AmbientTalk objects. AmbientTalk’s object instantiation protocol closely corresponds to class instantiation in class-based languages, except that the new object is a clone of an existing object, rather than an empty object allocated from a class. We further explain the semantics of object cloning in subsection Delegation and cloning.

Object's fields and methods are accessed as follows:

> aPoint.x
>>2
> aPoint.sumOfSquares()
>>13

Sending messages

In AmbientTalk, computation is expressed in terms of object sending messages to one another.

Note that AmbientTalk supports both traditional canonical syntax (e.g. o.m(a,b,c)) as well as keyworded syntax (e.g. o.at: key put: value) for method definitions and message sends.

Cloning and instantiation

Delegation and Dynamic Inheritance

Delegation and cloning

First-class Delegation

Encapsulation

at/tutorial/objects.1182939962.txt.gz · Last modified: 2007/06/27 12:28 (external edit)