clisp-devel

win32.lisp: why use full path to system dll?

[Hoehle, Joerg-C. <Joe...@t-...>]

Hi,

modules/bindings/win32.lisp contains
(defconstant system32 (ext:string-concat (ext:getenv "WINDIR") "\\system32\\"))
(defconstant kernel32 (ext:string-concat system32 "kernel32.dll"))

Why is this so?
o Is there a version of MS-Windows since 95 where the short form "kernel32.dll" does not suffice?

o Did anybody test this in conjunction with an image where the directory is at a different place on the new machine?
-- clisp has code to reopen shared libraries when restarting from an image file (which I never reviewed so far).

If not, I can do both test within a couple of days (I have a machine that boots from D:, and another with MS-Windows-95), but prefer knowledge about documented behaviour of the OS first to "tested on that night with that phase of the moon".

Regards,
	Jorg Hohle.

Re: win32.lisp: why use full path to system dll?

[Sam S. <sd...@gn...>]

> * Hoehle, Joerg-Cyril <Wbr...@g-...> [2005-07-05 13:42:24 +0200]:
>
> modules/bindings/win32.lisp contains
> (defconstant system32 (ext:string-concat (ext:getenv "WINDIR") "\\system32\\"))
> (defconstant kernel32 (ext:string-concat system32 "kernel32.dll"))
>
> Why is this so?

2005-06-06  Sam Steingold  <sd...@gn...>

	* modules/bindings/win32/win32.lisp: use full paths for :LIBRARY
	arguments (needed on cygwin)

this also could be a matter of security.

-- 
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.honestreporting.com> <http://www.camera.org>
<http://www.palestinefacts.org/> <http://www.mideasttruth.com/>
.sigs are like your face - rarely seen by you and uglier than you think