|
From: | Vadim V. Zhytnikov |
Subject: | Re: [Gcl-devel] Re: [Maxima] A bug in maxima-5.10.0.a |
Date: | Wed, 25 Oct 2006 11:47:30 +0300 |
User-agent: | Thunderbird 1.5.0.7 (Windows/20060909) |
Hi! I see from gcl code that *tmp-dir* is initialized by (gcl-temp-dir) only in one place - toplevel in gcl_cmpmain.lsp. And this works well for gcl itself but not for maxima and I really don't understand why. I see only two ways to resolve the problem on gcl's side: 1. Call get-temp-dir whem gazonk-name is called. Inefficient but reliable. 2. Insert *tmp-dir* reset somewhere in the initialization code which will be executed for any image created by gcl (like maxima executable).
I'm not sure this is really GCL bug. The point that gcl always resets *tmp-dir* on start up. But this doesn't happen with Maxima image. Probably Maxima itself should take care of resetting *tmp-dir*.Why is *tmp-dir* not assigned correctly in the Maxima image? If Maxima is preventing GCL from assigning this value correctly, or causing GCL to assign it incorrectly, it is a Maxima bug. Otherwise it is a GCL bug. On the whole I don't think Maxima should try to manage internal variables for each Lisp implementation. There is probably already some of that happening now, but I think we should steer away from doing more of it.
-- Vadim V. Zhytnikov <address@hidden> <address@hidden>
[Prev in Thread] | Current Thread | [Next in Thread] |