Differences

This shows you the differences between two versions of the page.

--- at:tutorial:objects [2007/06/27 14:24] – jorge
+++ at:tutorial:objects [2007/06/27 14:26] – jorge
@@ Line 28: / Line 28: @@
 </code>
-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 [[objects#Delegation_and_cloning|Delegation and cloning]].
+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.
 <note important>
-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.
+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.
 </note>
+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 [[objects#Delegation_and_cloning|Delegation and cloning]].
 ===== Sending messages =====