This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: Question about clisp version naming
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 23 Mar 2015 07:45:35 +0100
- Subject: Re: Question about clisp version naming
- Authentication-results: sourceware.org; auth=none
- References: <5500B536 dot 4050108 at cornell dot edu> <1426443595 dot 8104 dot 9 dot camel at cygwin dot com> <5505D57C dot 3040005 at cornell dot edu> <87twxm5azp dot fsf at Rainer dot invalid> <55060BF6 dot 80801 at cornell dot edu> <87k2ygbw7v dot fsf at Rainer dot invalid> <87fv94bveq dot fsf at Rainer dot invalid> <87bnjsbuhm dot fsf at Rainer dot invalid> <55073E93 dot 2030902 at cornell dot edu> <87vbhzph1g dot fsf at Rainer dot invalid> <5508998A dot 6040903 at cornell dot edu> <1426628400 dot 12464 dot 38 dot camel at cygwin dot com> <5508AD6F dot 60309 at cornell dot edu> <5508C42B dot 6030804 at dronecode dot org dot uk> <5508CCB4 dot 6080108 at cornell dot edu> <5508D02D dot 3080506 at cornell dot edu> <1426643243 dot 12464 dot 56 dot camel at cygwin dot com> <55097398 dot 10506 at cornell dot edu> <87oankah8y dot fsf at Rainer dot invalid> <550F4334 dot 3050503 at cornell dot edu> <550F7A20 dot 1030105 at cornell dot edu>
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 of a
> maxima executable. Is it really much slower to start maxima that way?
Not for me, but I'm using an SSD. I haven't yet tested on spinning rust
or over slow network. But I don't really think it makes much of a
difference, it seems it just has to open one more file than it would
otherwise. I'm not sure if there are other platforms for clisp that
can't dump executables, if so you might look at whether they remove the
corresponding code and/or warn or error out on an attempt to dump an
executable.
> I tried 'clisp -M maxima.mem', and it started up instantly. Whatever
> other overhead there is in the maxima script seems to be the same
> whether there's a maxima executable or not. But maybe I'm missing
> something.
As I said, I've revoked the maxima-exec-clisp package for now, so
whether you either come up with a solution for that problem or conclude
that dumping of executables isn't going to be supported on Cygwin, I'm
fine. For whatever reason, the exec stuff is the default for clisp and
building the non-exec had required some jumping through hoops (building
them both in one go wasn't even supported). But I've fixed that now.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables