[an error occurred while processing this directive]
<h1>ADM to EDEN Translator - Simon Yung's Work</h1>
<h2>Syntax of ADM</h2>
<p>
Because ADM accepts a richer algebra, the syntax of ADM has
deviated from the original specification of the Abstract Definitive
Machine.
</p>
<ul>
<li>Since Mike uses <code>[]</code> for parameterising variables, which crashes with
EDEN's list indexing operator, ADM uses <code>{}</code> instead for parameterising
variables.
</li>
<li>EDEN has no support for semi-evaluation (<code>| |</code>).  Therefore ADM
follows EDEN's tradition of using '<code><strong>is</strong></code>' and '<code>=</code>' for defining formula
variables and value variables.
</li>
<li>ADM supports two types of parameters.  For example:
<pre>
entity fielder(_F)(_P) {
definition
        pos{_F} is _P,
        ...
}
</pre>
The first group of parameters (one parameter only (<code>_F</code>) in this
case) has the same meaning as the parameters of the original Abstract
Definitive Machine - both for disambiguating the entity and for
parameter passing; the second group of parameters (also only one
parameter (<code>_P</code>) in this case) is only for parameter passing, it does not
contribute to the identification of entity.  For instance, the ADM
instantiation command:
<pre>
        fielder("sy")([0,0,0])
</pre>
will create a <code>fielder_sy</code> entity (and
a definition
<pre>
        pos_sy is [0,0,0]
</pre>
and so on) which will be deleted by the command:
<pre>
        delete fielder("sy")
</pre>
</li>
</ul>

[an error occurred while processing this directive]