Michael Schnell <[email protected]> hat am 9. Juni 2011 um 11:46 geschrieben:
> On 06/09/2011 10:58 AM, Henry Vermaak wrote:
> > You will corrupt the linked list that QueueAsyncCall() uses when you
> > call it from multiple threads, so you _must_ protect it.
> As QueueAsyncCall is specified exactly for this use, it needs to take
> care of this issue internally. Otherwise it obviously is buggy. I trust
> that the LCL developers did a decent job.
The only "specification" I found for TApplication.QueueAsyncCall is the fpdoc
entry:
Insert a given asynchronous call into the queue
Why do you think it is thread safe?
> (The list access needs to be protected even with a single worker thread,
> as the main thread removes elements in a concurrent access anyway.)
Mattias
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
