Hi,

the last example in Rory Walsh's intro to the csound api creates a
csound thread and then calls csoundScoreEvent from the main thread
without taking further precautions, while
CsoundPerformanceThread::ScoreEvent implementation enqueues a message
that is later unqueued by the performance thread, all in a perfect
thread-safe way. What is the real truth? Is csoundScoreEvent
thread-safe or not? In general, what thread safety warranties can be
assumed for the api?

Best regards
-Carlos

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net