Re: w32 bindings loadability

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

Sam,

several modules now use
  (require "exporting" "../../exporting")
This comes close, but IMHO the pathname should be some combination of merge-pathnames and *load-pathname* or *load-truename*).
"../../" depends on the current directory of CLISP, which is not TRT.

>-----Ursprungliche Nachricht-----
>> it would be nice if you could arrange for modules/bindings/win32.lisp
>> to be loadable anytime. Currently, its content: 
>>   (load "../../exporting")
>> causes this to fail. Even tricking *load-paths* did not help me.
>it should work now:
>clisp -i modules/exporting -i modules/bindings/win32/win32
The user does not care about the inner workings of some bindings file, i.e. exporting.lisp should be loaded transparently. I think *load-truename* + 2x :up (not :back) need be used.

Thanks you all for being very responsive to small improvements!

Regards,
	Jorg Hohle.