Recent changes to Classes

Classes modified by Will Pittenger

Will Pittenger — Sun, 16 Feb 2014 10:13:08 -0000

--- v10
+++ v11
@@ -7,7 +7,7 @@
 ~~~~
 :::text
 class MyClass
-    inherits MyBaseClass
+    extends MyBaseClass
     implements IIinterface
   public constructor
     ' Initialize the class with the default constructor
@@ -23,7 +23,7 @@
   private static var Boolean hidden = false
   private const i% = 3

-  ' If MyClass were declared with the abstract keyword, Test could be declared with the pure keyword instead of virtual
+  ' If MyClass were declared with the abstract keyword, Test could be declared with the abstract keyword instead of virtual
   protected virtual boolean Test
     return false

Classes modified by Will Pittenger

Will Pittenger — Sun, 16 Feb 2014 10:06:53 -0000

--- v9
+++ v10
@@ -5,6 +5,7 @@
 Classes in ASIL all derive from Object.  (Maybe moved into a namespace later.)  You use the following syntax to declare one:

 ~~~~
+:::text
 class MyClass
     inherits MyBaseClass
     implements IIinterface
@@ -35,6 +36,7 @@
 This is the what the declaration of the Object class will probably look like along with some related interfaces:

 ~~~~
+:::text
 class abstract Object
   public constructor
     ' Some code
@@ -54,15 +56,12 @@

   public function compare var const Object compareThis
     returns InstanceCompareResult
-     throws NotImplementedException

 interface ICloneable
   public function clone
     returns Object
-     throws NotImplementedException

 interface IEquatable
   public function equals var const Object compareThis
     returns Boolean
-    throws NotImplementedException
 ~~~~

Classes modified by Will Pittenger

Will Pittenger — Sun, 09 Feb 2014 13:47:49 -0000

--- v8
+++ v9
@@ -66,7 +66,3 @@
     returns Boolean
     throws NotImplementedException
 ~~~~
-
-File names associated with types
-================================
-Like Java, files must contain exactly one top level type per file.  (DASIL source code files can have global code and/or procedures.  But types must one per file.)  The file name must match the type name.  However, large complex types can be split amongst several source code files.  Such files must use the naming convention typename.sectionname.asil.  That will cause the compiler to automatically combine the pieces.

Classes modified by Will Pittenger

Will Pittenger — Thu, 06 Feb 2014 17:28:04 -0000

--- v7
+++ v8
@@ -32,7 +32,7 @@

 The Object class 
 ================
-This is the what the declaration of the Object class will probably look like:
+This is the what the declaration of the Object class will probably look like along with some related interfaces:

 ~~~~
 class abstract Object
@@ -41,29 +41,30 @@

   public virtual function toString
       returns String
-    return getType.toString
+    return type.toString

-  public static final Type type ' See [Reflection]
+  public static final TypeInstance type ' See [Reflection]

+interface IComparable
+    inherits IEquatable
   public enum InstanceCompareResult
     lessThan
     equal
     greaterThan

-  public virtual function clone
-      returns Object
-      throws NotImplementedException
-    throw new NotImplementedException
+  public function compare var const Object compareThis
+    returns InstanceCompareResult
+     throws NotImplementedException

-  public virtual function compare var const Object compareThis
-      returns InstanceCompareResult
-      throws NotImplementedException
-    throw NotImplementedException
+interface ICloneable
+  public function clone
+    returns Object
+     throws NotImplementedException

-  public virtual function equals var const Object compareThis
-      returns Boolean
-      throws NotImplementedException
-    throw NotImplementedException
+interface IEquatable
+  public function equals var const Object compareThis
+    returns Boolean
+    throws NotImplementedException
 ~~~~

 File names associated with types

Classes modified by Will Pittenger

Will Pittenger — Wed, 05 Feb 2014 10:03:50 -0000

--- v6
+++ v7
@@ -68,4 +68,4 @@

 File names associated with types
 ================================
-Like Java, files must contain exactly one top level type per file.  (DASIL source code files can have global code and/or procedures.  But types must one per file.)  The file name must match the type name.  However, large complex types can be split amongst several source code files.  Such files must use the naming convention typename.sectionname.asil.
+Like Java, files must contain exactly one top level type per file.  (DASIL source code files can have global code and/or procedures.  But types must one per file.)  The file name must match the type name.  However, large complex types can be split amongst several source code files.  Such files must use the naming convention typename.sectionname.asil.  That will cause the compiler to automatically combine the pieces.

Classes modified by Will Pittenger

Will Pittenger — Wed, 05 Feb 2014 10:01:12 -0000

--- v5
+++ v6
@@ -43,7 +43,7 @@
       returns String
     return getType.toString

-  public static final Type type ' See [[Reflection]]
+  public static final Type type ' See [Reflection]

   public enum InstanceCompareResult
     lessThan

Classes modified by Will Pittenger

Will Pittenger — Wed, 05 Feb 2014 09:59:41 -0000

--- v4
+++ v5
@@ -1,6 +1,7 @@
+[TOC]
+
 General discussion and sample
 =============================
-
 Classes in ASIL all derive from Object.  (Maybe moved into a namespace later.)  You use the following syntax to declare one:

 ~~~~
@@ -30,8 +31,7 @@
 ~~~~

 The Object class 
-----------------
-
+================
 This is the what the declaration of the Object class will probably look like:

 ~~~~
@@ -65,3 +65,7 @@
       throws NotImplementedException
     throw NotImplementedException
 ~~~~
+
+File names associated with types
+================================
+Like Java, files must contain exactly one top level type per file.  (DASIL source code files can have global code and/or procedures.  But types must one per file.)  The file name must match the type name.  However, large complex types can be split amongst several source code files.  Such files must use the naming convention typename.sectionname.asil.

Classes modified by Will Pittenger

Will Pittenger — Tue, 04 Feb 2014 14:38:50 -0000

--- v3
+++ v4
@@ -39,9 +39,9 @@
   public constructor
     ' Some code

-  public function virtual toString
+  public virtual function toString
       returns String
-    return getType().toString
+    return getType.toString

   public static final Type type ' See [[Reflection]]

Classes modified by Will Pittenger

Will Pittenger — Tue, 04 Feb 2014 14:36:56 -0000

--- v2
+++ v3
@@ -43,8 +43,25 @@
       returns String
     return getType().toString

-  public function getType
-      return Type ' See reflection
+  public static final Type type ' See [[Reflection]]

-  public static final Type type
+  public enum InstanceCompareResult
+    lessThan
+    equal
+    greaterThan
+
+  public virtual function clone
+      returns Object
+      throws NotImplementedException
+    throw new NotImplementedException
+
+  public virtual function compare var const Object compareThis
+      returns InstanceCompareResult
+      throws NotImplementedException
+    throw NotImplementedException
+
+  public virtual function equals var const Object compareThis
+      returns Boolean
+      throws NotImplementedException
+    throw NotImplementedException
 ~~~~

Classes modified by Will Pittenger

Will Pittenger — Tue, 04 Feb 2014 14:20:40 -0000

--- v1
+++ v2
@@ -1,3 +1,6 @@
+General discussion and sample
+=============================
+
 Classes in ASIL all derive from Object.  (Maybe moved into a namespace later.)  You use the following syntax to declare one:

 ~~~~
@@ -26,6 +29,9 @@
     return 7 ' 7 additional words
 ~~~~

+The Object class 
+----------------
+
 This is the what the declaration of the Object class will probably look like:

 ~~~~
@@ -39,4 +45,6 @@

   public function getType
       return Type ' See reflection
+
+  public static final Type type
 ~~~~