Ken Brown writes:
> And indeed it does. I've still got a couple of things to clean up,
> but I expect to upload a new clisp soon that no longer uses lisp.dll.
> I hope that will solve the Maxima problem
It doesn't… Instead of lisp.dll it now requires lisp.exe to be in $PATH
and it produces an exe
On 3/22/2015 4:50 PM, Achim Gratz wrote:
Ken Brown writes:
And indeed it does. I've still got a couple of things to clean up,
but I expect to upload a new clisp soon that no longer uses lisp.dll.
I hope that will solve the Maxima problem
It doesn't… Instead of lisp.dll it now requires lisp.ex
On 3/22/2015 6:33 PM, Ken Brown wrote:
On 3/22/2015 4:50 PM, Achim Gratz wrote:
Ken Brown writes:
And indeed it does. I've still got a couple of things to clean up,
but I expect to upload a new clisp soon that no longer uses lisp.dll.
I hope that will solve the Maxima problem
It doesn't… Ins
Ken Brown writes:
>> So maybe you could dump a memory image maxima.mem and start it with a
>> script that calls 'clisp -M maxima.mem'.
I'm already doing that. :-)
> I just took a look at the maxima package, and it seems that you
> already use a script that does something like this in the absence
