at:tutorial:objects
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
at:tutorial:objects [2007/06/29 08:32] – jorge | at:tutorial:objects [2007/07/18 18:09] – jorge | ||
---|---|---|---|
Line 4: | Line 4: | ||
In AmbientTalk, | In AmbientTalk, | ||
classes. Rather, they are either created ex-nihilo or by cloning | classes. Rather, they are either created ex-nihilo or by cloning | ||
- | and adapting existing objects, | + | and adapting existing objects, |
The following code illustrates the ex-nihilo creation of an object: | The following code illustrates the ex-nihilo creation of an object: | ||
< | < | ||
- | > def Point := object: { | + | def Point := object: { |
- | def x := 0; | + | def x := 0; |
- | def y := 0; | + | def y := 0; |
- | def init(aX,aY) { | + | def init(aX,aY) { |
- | x := aX; | + | x := aX; |
- | y := aY; | + | y := aY; |
- | }; | + | }; |
- | def sumOfSquares() { x*x + y*y }; | + | def sumOfSquares() { x*x + y*y }; |
- | } | + | } |
- | >>< | + | |
</ | </ | ||
- | As all definitions in AmbientTalk, objects, fields and methods are defined using the **def** keyword. Fields are defined using a '' | + | The above code defines an // |
- | < | + | In the example above, the state of the point object is composed of '' |
- | AmbientTalk not only supports traditional canonical syntax (e.g. '' | + | |
+ | < | ||
+ | As already explained in the [[at: | ||
+ | |||
+ | For Smalltalk/ | ||
</ | </ | ||
- | In the example above, the state of the '' | + | ===== Sending messages ===== |
+ | In AmbientTalk, computation | ||
< | < | ||
- | > def aPoint := Point.new(2,3) | + | > Point.x |
- | >>< | + | >>0 |
+ | > Point.sumOfSquares() | ||
+ | >>0 | ||
</ | </ | ||
- | Every object understands | + | This code shows two messages sent to the point object |
- | ===== Sending messages | + | Note that the " |
- | In AmbientTalk, computation is expressed in terms of objects | + | |
+ | ===== Cloning and instantiation | ||
+ | As noted above, AmbientTalk | ||
< | < | ||
- | > aPoint.x | + | def anotherPoint := Point.new(2,3) |
- | >>2 | + | |
- | > aPoint.sumOfSquares() | + | |
- | >>13 | + | |
</ | </ | ||
- | This code shows two messages sent to the '' | + | Every object understands |
- | ===== Cloning and instantiation ===== | + | < |
- | As said before in this section, AmbientTalk objects are created [[objects# | + | > anotherPoint.x |
+ | >> 2 | ||
+ | > Point.x | ||
+ | >> 0 | ||
+ | > anotherPoint.x := 3 | ||
+ | >> nil | ||
+ | > Point.x | ||
+ | >> 0 | ||
+ | </ | ||
+ | < | ||
+ | AmbientTalk' | ||
+ | </ | ||
+ | AmbientTalk also provides a '' | ||
+ | |||
+ | < | ||
+ | def clonedPoint := clone: Point | ||
+ | > clonedPoint.x | ||
+ | >> 0 | ||
+ | > clonedPoint.x := 2 | ||
+ | >> nil | ||
+ | > Point.x | ||
+ | >> 0 | ||
+ | </ | ||
+ | |||
+ | ===== Delegation and Cloning ===== | ||
+ | |||
+ | In order to support code reuse and modular extensions between objects, AmbientTalk features // | ||
+ | |||
+ | Delegation implies that, if a message is sent to an object, but that object has no definition for the message' | ||
+ | |||
+ | AmbientTalk distinguishes between **two kinds** of delegation relationships, | ||
+ | |||
+ | An **IS-A** delegation relationship between two objects signifies that the child object " | ||
+ | |||
+ | < | ||
+ | def Point3D := extend: Point with: { | ||
+ | def z := 0; | ||
+ | def sumOfSquares() { | ||
+ | super^sumOfSquares() + z*z; | ||
+ | }; | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | In this example, '' | ||
+ | |||
+ | A **SHARES-A** relationship between two objects signifies that an object only delegates to another object purely for reasons of code or state sharing. The delegation link has no other semantics, and conceptually both parent and child can exist without one another. | ||
+ | |||
+ | The following code shows how to extend objects with a **SHARES-A** delegation relationship. It uses the '' | ||
+ | |||
+ | < | ||
+ | def Collection := share: Enumerable with: { | ||
+ | def elements := []; | ||
+ | ... | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | In this code example, the '' | ||
+ | |||
+ | The **IS-A** and **SHARES-A** delegation relationships differ in their semantics for cloning child objects. Whereas cloning an **IS-A** child also clones its parent, a **SHARES-A** child shares its parent object with the clonee (see the figure below). | ||
+ | |||
+ | {{: | ||
+ | |||
+ | This cloning semantics reinforces the semantics of **IS-A** as promoting a unique link between a parent and a child object. **IS-A** delegation most closely corresponds to class-based inheritance. | ||
===== Delegation and Dynamic Inheritance ===== | ===== Delegation and Dynamic Inheritance ===== | ||
- | ===== Delegation | + | In AmbientTalk, |
+ | |||
+ | Because '' | ||
+ | |||
+ | < | ||
+ | def openConnection := object: { | ||
+ | def send(msg) { ... }; | ||
+ | }; | ||
+ | def closedConnection := object: { | ||
+ | def send(msg) { ... }; | ||
+ | }; | ||
+ | def connection := object: { | ||
+ | def init() { | ||
+ | super := closedConnection; | ||
+ | }; | ||
+ | def open() { | ||
+ | super := openConnection; | ||
+ | }; | ||
+ | def close() { | ||
+ | super := closedConnection; | ||
+ | }; | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | In the above example, the '' | ||
+ | |||
+ | < | ||
+ | In AmbientTalk, | ||
+ | </ | ||
===== First-class Delegation ===== | ===== First-class Delegation ===== | ||
+ | |||
+ | AmbientTalk provides a special message-sending operator '' | ||
+ | |||
+ | < | ||
+ | def Enumerable := object: { | ||
+ | def collect: closure { | ||
+ | def c := self.new(); | ||
+ | self.each: { |v| | ||
+ | closure(v); | ||
+ | }; | ||
+ | }; | ||
+ | }; | ||
+ | def Array := object: { | ||
+ | def elements := []; | ||
+ | def add(v) { elements := elements + [v]; self }; | ||
+ | def collect: closure { | ||
+ | Enumerable^collect: | ||
+ | }; | ||
+ | def each: clo { | ||
+ | 1.to: elements.length + 1 do: { |i| | ||
+ | elements[i] := clo(elements[i]); | ||
+ | }; | ||
+ | }; | ||
+ | }; | ||
+ | </ | ||
+ | |||
+ | A message sent to an object using the '' | ||
+ | |||
+ | < | ||
+ | > Array.add(1).add(2).add(3) | ||
+ | >> < | ||
+ | > def c := Array.collect: | ||
+ | >> < | ||
+ | > c.each: { |v| system.println(v)} | ||
+ | 2 | ||
+ | 3 | ||
+ | 4 | ||
+ | >>nil | ||
+ | </ | ||
+ | |||
+ | Of course, the example above is a bit contrived: we could have just assigned '' | ||
+ | |||
+ | Having described the semantics of '' | ||
+ | |||
+ | < | ||
+ | def Point3D := extend: Point with: { | ||
+ | def z := 0; | ||
+ | def init(aX, aY, aZ) { | ||
+ | super^init(aX, | ||
+ | z := aZ; | ||
+ | }; | ||
+ | }; | ||
+ | </ | ||
+ | |||
+ | <note warning> | ||
+ | AmbientTalk, | ||
+ | |||
+ | Keep in mind, however, that '' | ||
+ | </ | ||
===== Encapsulation ===== | ===== Encapsulation ===== | ||
+ | AmbientTalk has no notion of " | ||
+ | |||
+ | < | ||
+ | def makeBankAccount(balance) { | ||
+ | object: { | ||
+ | def deposit(amnt) { | ||
+ | balance := balance + amnt; | ||
+ | " | ||
+ | }; | ||
+ | } | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | Because the bank account object encapsulates its '' | ||
+ | |||
+ | < | ||
+ | > makeBankAccount(100).balance; | ||
+ | >> | ||
+ | < | ||
+ | </ |
at/tutorial/objects.txt · Last modified: 2013/05/17 20:23 by tvcutsem