On Tue, 04 Oct 2005 20:40:56 +0200, Edi Weitz edi@agharta.de wrote:
Yes, that /was/ the culprit. It turns out this is a bug in LW which'll be fixed soon:
http://thread.gmane.org/gmane.lisp.lispworks.general/4604
Until then there's no immediate solution other than using undocumented functions like ENCODE-LISP-STRING which don't work well with delivery.
OK, thanks to LispWorks support there is a better solution now. If you're using LispWorks 4.4.5 on Windows or Linux (/not/ on OS X as the problem doesn't happen there) you can send an email to
lisp-support@lispworks.com
asking for the patch SYSTEM-CONS-FREE-CHAIN which you'll get for free. Please make sure to use the "Report Bug" command from the LW IDE to include a full bug report form.
The new 0.8.3 release is just intended to alert users who don't read this mailing list of this problem.
ChangeLog:
Version 0.8.3 2005-10-10 Alert LW users that a patch for OCTETS-TO-STRINGS is available (thanks to LispWorks support)
Download:
http://weitz.de/files/tbnl.tar.gz
Cheers, Edi.