On Wed, 1 Aug 2007, Stephen Wilson wrote: | Gabriel Dos Reis <[EMAIL PROTECTED]> writes: | | > Stephen Wilson <[EMAIL PROTECTED]> writes: | > | > [...] | > | > | There is also the question of being able to provide the compiler | > | components in the form of a library which can be used by other aspects | > | Axiom. For example, one would be able to use the new parser and | > | (forthcoming) type checker to support an IDE. | > | > People may note that, in Axiom as of today, one can already get the | > syntax tree from both the old and the new parsers, and in fact use the | > parser as a library -- as has been done the algorithmic | > differentiation project. You don't need to wait for a | > functional new compiler to do that. | | Can it incrementally parse input as the user is typing, thus making it | a usable component in an IDE? Is the AST itself specified? Does it | the representation past the lexical analysis phase contain line and | column number information? Is the current implementation easily | modifiable and extensible?
You can answer all those questions by looking at the source code. The Axiom interpreter uses the new compiler/parser. The Axiom compiler uses the old compiler/parser. The new compiler/parser can also compiler library codes -- through the connection is not present in Silver, but requires only few lines of code. -- Gaby _______________________________________________ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom-developer
