Re: thread safety

[email protected] Thu, 24 Apr 2008 08:45:41 +0900
Newsgroups gmane.lisp.matlisp.user
Message-ID <[email protected]>
"Raymond Toy (RT/EUS)" <[email protected]> writes:

> Evan Monroig wrote:
>> Hi,
>>
>> I have been using matlisp for a little while now, and I started to
>> look inside matlisp files to see if it was thread-safe.
>>
>> One issue that I have found is that functions like
>> DGEEV-WORKSPACE-INQUIRY are closures around matrices of size one
>> which are used to store the size of the work matrix.
>>
>> If I call DGEEV-WORKSPACE-INQUIRY simultaneously in several threads,
>> it might happen that the values that are read/written in this matrix
>> will be polluted by the other threads.
>
> Yes, that's a problem.  At the time these were written, I guess I
> could bear to cons up a single-element matrix just for this.  But now
> that threaded Lisp's are becoming more common, we should change this.
>
> Thanks for the reminder.  I'll look into fixing this soon.

Thanks for your answer.  Please let me know if you would like a patch
for this, although it might be less work for you to do the modifications
than handle a patch in this case.

Evan

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone