Changes between Version 19 and Version 20 of InterpreterGuide

Timestamp:

06/18/08 18:54:24 (17 months ago)

Author:

sukyoungryu

Comment:

--

InterpreterGuide

@@ -7 +7 @@
 
 It can be run from ant, from the command line, or as junit tests.  The plan is to, as much as possible, allow Fortress programs to run as if they were interpreted (without explicit compile, link, and run steps that a user can do wrong), and perform compiler-like operations "behind the curtain".  This will change over time as the implementation acquires platform-specific and application-specific optimizations -- the caches will become more like the "Fortresses" in the original language plan, and will acquire operations more interesting than just get, put, and is-up-to-date.  ''Explain in more detail''
+
+== AST nodes ==
+The Fortress AST nodes are automatically generated by the [http://sourceforge.net/projects/astgen ASTGen] tool from the [source:trunk/ProjectFortress/astgen/Fortress.ast AST node hierarchy description].  Among other language constructs, Fortress expressions are represented as subclasses of the abstract class {{{Expr}}}.  The {{{Expr}}} node hierarchy is particularly interesting because most of the Fortress type checking deals with the subclasses of {{{Expr}}}.  Some of the nodes are created internally and some of the nodes are desugared away after a particular phase.  Detailed information about [wiki:ExprNodeHierarchy the Expr node hierarchy] is available.
 
 == Phase structure ==
@@ -143 +146 @@
 There's no discussion of structure of phases as visitors over ASTs.
 
-We should have discussion the AST nodes (which nodes are top level, etc.) ''Separate page''
-
 We need a description of each package and what's contained in it, as well as other important directories. ''Separate page''