Hm, an afterthought: I'm not quite sure whether what
Martin Rubey thought:
> I would also think that it is a bad idea to do the dependency checking
> outside
> of axiom.
makes sense.
Here a first shot at organizing the things axiom should consist of:
* a compiler
* an interpreter
* a user interface
* hyperdoc
What does the interpreter do?
* parse the input
* find appropriate signatures
* if it is
a call to a compiled function: evaluate
a function definition: add it to the workspace
Currently, the parser of the interpreter and the parser of the compiler are
different. For example, you cannot define packages, domains or categories in
the interpreter.
In fact, this is also a question of future direction, since I hope very much
that Aldor will become *the* language for Axiom.
Maybe it would make sense to make the type inference as much independent of the
interpreter as possible. It seems, that quite a few type coercions are defined
for the interpreter only. Why aren't they in the algebra? One example is the
coercion from UP to POLY, I think.
Martin
_______________________________________________
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listinfo/axiom-developer
