Differences

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

--- at:reference:reference [2008/07/07 18:23] – updated tvcutsem
+++ at:reference:reference [2020/02/11 13:21] (current) – elisag
@@ Line 2: / Line 2: @@
-<box 70% round orange><html><center><font size="+1"><a href="http://prog.vub.ac.be/amop/at2langref">View the language reference</a></font></center></html></box>
+<box 70% round orange><html><center><font size="+1"><a href="http://soft.vub.ac.be/amop/at2langref">View the language reference</a></font></center></html></box>
-**How to read the documentation:** the above language reference is a modified Javadoc documentation extracted from the interpreter's source code. The documentation talks about classes, packages and interfaces. Of course, these concepts do not exist in AmbientTalk. However, at the implementation-level, a class in the interpreter corresponds to an abstract data type provided to the AmbientTalk programmer. Its methods correspond to the methods which the AmbientTalk programmer can invoke upon them.
+**How to read the documentation:** the above language reference is a modified Javadoc documentation extracted from the interpreter's source code. The documentation talks about classes, packages and interfaces. Of course, these concepts do not exist in AmbientTalk. However, at the implementation-level, a class in the interpreter corresponds to an abstract data type provided to the AmbientTalk programmer. Its methods correspond to the methods which the AmbientTalk programmer can invoke upon them. Thus, if you want to look up what methods are applicable on numbers, check the methods of class ''Number''.
-Thus, if you want to look up what methods are applicable on numbers, check the methods of class ''Number''. The only exception to this rule is the ''Object'' class, which does not document the operations applicable on all objects, but rather the operations applicable on all object //mirrors// (i.e. it documents AmbientTalk's MOP).
+Methods that take an ''Object[]'' as an argument should be interpreted as taking an arbitrary number of arguments (i.e. an ''@args'' parameterlist in AmbientTalk).
+Note that the class hierarchy does not accurately reflect the delegation hierarchy in between objects. All objects eventually delegate to Nil, so all methods defined on Nil are applicable on all objects.
 The language reference documents:
@@ Line 13: / Line 15: @@
   * ''edu.vub.at.objects.grammar'': the structure of abstract syntax tree objects (for metaprogramming)
   * ''edu.vub.at.objects.natives'': the object marked ''LexicalRoot'' documents all operations available in the global lexical scope (top-level definitions, accessible unqualified). The object marked ''System'' documents the ''system'' native object.
-  * ''Object'': documents all operations available on mirrors (i.e. all operations available at the meta-level)
-Still to be added:
+The most important functionality available in the standard library shipped with the AmbientTalk distribution is summarized in the tutorial's [[:at:tutorial:appendix|appendix]] and its source code is accessible [[ https://gitlab.soft.vub.ac.be/ambienttalk/atlib |here.]]
-  * The functionality available in the system library shipped with the distribution.