Re: How CLSQL finds and loads foreign libraries

On Thu, 7 Jul 2005 13:58:52 +0200, "Hoehle, Joerg-Cyril" <[email protected]> wrote:

>> That's a pity.  Isn't there a way for CLISP to find out whether
>> it's on Cygwin and only then demand the full path.
>
> How should that work from within e.g. a library like cl-sql?  Your
> use of "demand" is unclear to me.

That was a misunderstanding then.  If one can still provide a relative
path for "native" Win32 (that's what I understand from the rest of
your message) it's fine for me.

Nevertheless it's kind of funny that only a few days after CLSQL/UFFI
had incorporated my patches for relative pathnames CMUCL as well as
CLISP (partly) ceased to support this feature... :(

Cheers,
Edi.