[an error occurred while processing this directive]
Since we are talking about two implementations of the same
application, I would like to start with the following distinction. Am
here refers to the original interpreter for the Abstract Definitive
Machine described in Mike Slade's thesis and adm refers Simon
Yung's translator to EDEN. The following shows the relative strength and
weaknesses for the two implementations.
| + | Parallel actions |
| + | Conflict detection |
| + | More reliable |
| + | Has semi-evaluation operator (| |) |
| - | Limited algebra (only has integer and boolean) |
| - | Restricted interface to definitive notations |
| + | Accept most (if not all) EDEN definitions |
| + | Fully supported by other definitive notations |
| + | More advanced parameter specification |
| - | Sequential execution |
| - | No conflict detection |
| - | Poor handling of entity deletion |
| - | Not fully tested yet |
The principle aim of translating ADM to EDEN is to enhance the
underlying algebra of Abstract Definitive Machine. With ADM it is possible
to program more sophisticated simulations.
However, because EDEN is basically sequential, the true power of
Abstract Definitive Machine cannot be utilised with the current
implementation of ADM. The choice of using am or adm
is up to the user to determine.