[usocket-devel] CLISP condition system change

[Vladimir Sedach]

I built CLISP from the latest stable sources
(https://sourceforge.net/project/platformdownload.php?group_id=1355).
The only option I provided to ./configure was
--with-threads=POSIX_THREADS. The reason threads are not on by default
is that defining CLOS classes and modifying hash-tables isn't
thread-safe and might cause segfaults, but that's the case with all
other CL implementations as well.

Vladimir

2012/2/17 Chun Tian (binghe) <binghe.lisp at gmail.com>:
> Hi, Vladimir
>
> Thanks for this patch, I'll make it part of new USOCKET release.
>
> By the way, where can I get a "official" multi-theaded CLISP distribution with recommended build options?
>
> --binghe
>
> 在 2012-2-17，09:09， Vladimir Sedach 写道：
>
>> Hi,
>>
>> In the repository version of CLISP, there's been some changes to the
>> condition class hierarchy. usocket/backend/clisp.lisp line 685 reads:
>>
>>      (system::simple-os-error
>>
>> Changing that to:
>>
>>      (ext:os-error
>>
>> Should work for the current version (2.49 - simple-os-error inherited
>> from os-error and the usocket condition argument accessors are
>> otherwise generic) and the upcoming CLISP version.
>>
>> Vladimir
>>
>> _______________________________________________
>> usocket-devel mailing list
>> usocket-devel at common-lisp.net
>> http://lists.common-lisp.net/cgi-bin/mailman/listinfo/usocket-devel
>