[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Axiom-developer] Axiom/Aldor
From: |
Martin Rubey |
Subject: |
Re: [Axiom-developer] Axiom/Aldor |
Date: |
Wed, 12 Jan 2005 11:40:16 +0100 |
Dear Peter, Tim,
Peter Broadbery writes:
> On Tue, 2005-01-11 at 14:30 +0100, Martin Rubey wrote:
> > Dear Peter,
> >
> > this is just great stuff -- nearly... I had to try it out right away, but I
> > experienced two problems.
> >
> > the minor one is, that )co inside axiom still does not work:
> >
> > (1) ->
> > (1) -> )co test.as
> > Compiling AXIOM source code from file
> > /home/rubey/martin/Axiom/test.as using AXIOM-XL compiler and
> > options
> > -O -Fasy -Fao -Flsp -laxiom -Mno-AXL_W_WillObsolete -DAxiom -Y
> > $AXIOM/algebra
> > Use the system command )set compiler args to change these
> > options.
> >
> > >> System error:
> > NIL is not of type STRING.
>
>
> ln -s $ALDORROOT $AXIOM/compiler may help here. fixing i-syscmd.boot to
> produce a nice error would be nice, I guess.
I tried that, but it won't work. Tim, is there a way to trace what's happening?
Note that both $ALDORROOT and $AXIOM were set correctly. In other words, the
link above produced a directory "compiler" in "axiom/mnt/linux", containing the
following directories of Aldor: bin/ doc/ include/ lib/ src/ tests/
> The .as file isn't in CVS (the file is compiled - don't be fooled by the
> readable coding style)
Sorry, my mistake. Only lsp files. By the way, there i *lots* of stuff in the
directories under /lsp/ccl/src, some look like they could be really useful...
Tim: could you rename them to .pamphlet and correct the \usepackage line in
each one of them? Thanks!
> > (1) -> fact(5)$Test
> >
> > (1) 120
> > Type:
> > PositiveInteger
> > (2) -> fact(4)$Test
> >
> > >> System error:
> > #<vector 08cf4150> is not of type LIST.
> >
>
> Fixed by the patch I send earlier (I hope)...
Yes indeed! (I found that there was only one line you had to comment out?)
> The significant bit is removing an unbound variable from as.boot, the
> rest is to fix the )co command (obviously not bullet proof), and the .ap
> file generation.
>
> In terms of aldor internal knowledge, you don't need that much, the hard
> work is on the axiom side. The trick is to load all the aldor runtime
> env interpreted and see what breaks (this includes daase.lisp, as.clisp
> & interop.clisp, plus the aldor .lsp files). This stuff used to vaguely
> work, so putting it back in shape can't be too bad.
In another mail, you wrote:
> As long as you don't use the sig. from the interpreter, you will be ok
> (which misses the point,, I know). As far as fixing the error, not really,
> I don't know the axiom interpreter that well. Finding how & where the type
> is substituted would be a good start [There must be someone who does...]
Who could this be? It would be just wonderful to get this working!
Thanks a million times,
Martin
Re: [Axiom-developer] Axiom/Aldor, Martin Rubey, 2005/01/11