Hi,
Even though the api documentation doesn't mention it, I've found that join-thread is expected to have a value of the thread's function in some lisp implementations.
(asdf:test-system :sqlite) always fails in concurrent access test since it checks return values of join-thread and join-thread's value is nil in current implementation for Allegro CL. The followings are changes I've made to correct this problem, so please have a look at it.
https://bitbucket.org/kmizumar/bordeaux-threads/changeset/5de529f36b92 https://bitbucket.org/kmizumar/bordeaux-threads/changeset/549bbcdcf794
Thanks in advance and sorry for my poor English, I'm still learning it.
Kiyoshi -- Kiyoshi Mizumaru kiyoshi.mizumaru@gmail.com
On Mon, 2012-03-26 at 00:35 +0900, Kiyoshi Mizumaru wrote:
Hi,
Even though the api documentation doesn't mention it, I've found that join-thread is expected to have a value of the thread's function in some lisp implementations.
(asdf:test-system :sqlite) always fails in concurrent access test since it checks return values of join-thread and join-thread's value is nil in current implementation for Allegro CL. The followings are changes I've made to correct this problem, so please have a look at it.
https://bitbucket.org/kmizumar/bordeaux-threads/changeset/5de529f36b92 https://bitbucket.org/kmizumar/bordeaux-threads/changeset/549bbcdcf794
Thanks in advance and sorry for my poor English, I'm still learning it.
I committed a different implementation that uses a hash-table to store the return values, which doesn't require us to create a new process class. Please test and is some test fails, send the output
bordeaux-threads-devel@common-lisp.net