Differences

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

--- at:tutorial:modular [2010/06/15 17:01]
tvcutsem *
+++ at:tutorial:modular [2013/02/26 15:52]
cfscholl
@@ Line 266: / Line 266: @@
 Type tags can best be compared to empty Java interface types. Such empty interfaces are sometimes used in Java purely for the purposes of marking an object. Examples are ''java.io.Serializable'' and ''java.lang.Cloneable''. An empty interface type can be implemented by any class (object) and hence only serves the purpose of distinguishing objects by type (by means of ''instanceof'' in Java).
 </note>
 ==== Native Type Tags ====
-The module ''/.at.types'' shipped with the system library contains the type definitions of the native data types of the interpreter. These type tags can be used to perform type tests on objects, for example:
+The module ''/.at.lang.types'' shipped with the system library contains the type definitions of the native data types of the interpreter. These type tags can be used to perform type tests on objects, for example:
 <code>
-is: 1 taggedAs: /.at.types.Number
+is: 1 taggedAs: /.at.lang.types.Number
 >> true
-is: "foo" taggedAs: /.at.types.Text
+is: "foo" taggedAs: /.at.lang.types.Text
 >> true
 </code>
-The type ''/.at.types.Isolate'' can be used to mark an object as an isolate. Isolate objects are similar to serializable Java objects. They are explained when introducing concurrent programming in [[at:tutorial:actors|a later chapter]].
+The type ''/.at.lang.types.Isolate'' can be used to mark an object as an isolate. Isolate objects are similar to serializable Java objects. They are explained when introducing concurrent programming in [[at:tutorial:actors|a later chapter]].
 ==== Type tags as annotated message sends ====
@@ Line 290: / Line 291: @@
 In the [[at:tutorial:actors|chapter on actors]] we use this feature to distinguish purely asynchronous message sends from so-called //future-type// message sends. If the message send is annotated with the ''FutureMessage'' type tag, the asynchronous send returns a future, otherwise it returns ''nil''.
 ===== Exception Handling =====
@@ Line 313: / Line 315: @@
 </code>
-Note that a new instance of an object named ''XDivisionByZero'' is raised, not the type tag ''DivisionByZero'' itself. An exception is any object that is tagged with (a subtype of) the ''lobby.at.types.Exception'' type tag. By convention, an exception should have the fields ''message'' and ''stackTrace''. The exception module found under ''lobby.at.exceptions'' contains an auxiliary function named ''createException'' which takes a type tag as argument and returns a new prototype exception object. For example:
+Note that a new instance of an object named ''XDivisionByZero'' is raised, not the type tag ''DivisionByZero'' itself. An exception is any object that is tagged with (a subtype of) the ''lobby.at.lang.types.Exception'' type tag. By convention, an exception should have the fields ''message'' and ''stackTrace''. The exception module found under ''lobby.at.lang.exceptions'' contains an auxiliary function named ''createException'' which takes a type tag as argument and returns a new prototype exception object. For example:
 <code>
-deftype DivisionByZero <: lobby.at.types.Exception;
+deftype DivisionByZero <: lobby.at.lang.types.Exception;
-def XDivisionByZero := lobby.at.exceptions.createException(DivisionByZero);
+def XDivisionByZero := lobby.at.lang.exceptions.createException(DivisionByZero);
 </code>
@@ Line 343: / Line 345: @@
     system.println(exc.message);
   };
-})
+} taggedAs: [/.at.lang.types.Handler])
 </code>

Ambient-Oriented Programming

User Tools

Site Tools

Differences

Page Tools