|
From: | Ralf Hemmecke |
Subject: | Re: [Axiom-developer] merge branches/daly to trunk |
Date: | Tue, 05 Jun 2007 15:36:05 +0200 |
User-agent: | Thunderbird 2.0.0.0 (X11/20070326) |
| > (1) we should have standalone bootsys, that can translate, compile | > Boot codes. It should be able to create standalone executable from | > Boot+Lisp programs.
| > Currently, I have (1) plus a standalone depsys that can create executable | > from Lisp+Boot programs, but my hope is that depsys will die soon.| | Would that mean that Aldor->Lisp->executable should work?
Could you elaborate on what you mean by that phase?
I meant that using (1) could help to get something like the equivalent of AldorUnit running for the Axiom library. I don't know how much that makes sense, but it might help us to introduce unit testing to Axiom.
I imagine that testcases could be written in Aldor like for AldorUnit, but then we need to take libaxiom, libaldorunit (which was compiled against libaxiom) and produce an executable TestSuite program. That would just be similar to what is done now with aldorunit.
It basically works like that: 1) write a couple of testcases. 2) let a program generate a wrapper file that collects all these cases into a TestSuite.as file. 3) Compile TestSuite.as (using libaxiom and libaldorunit as underlying libraries) and arrive at an executable.No interpreter would be needed here. It would simply test the things in libaxiom.
The Aldor compiler would be used to produce LISP. (Or use the SPAD compiler, if that works with a well-specified (and close to Aldor) input language.) From there I understood you can go on via (1) to produce an executable.
Ralf
[Prev in Thread] | Current Thread | [Next in Thread] |