On Wednesday, July 16, 2003, at 05:55  AM, Xavier Leroy wrote:

> That's the crux of the problem, indeed.  I looked at the PortAudio
> tutorial and found this little gem:
>
>   Your callback function is often called by an interrupt, or low level
>   process so you should not do any complex system activities like
>   allocating memory, or reading or writing files, or printf(). Just
>   crunch numbers and generate audio signals.

I'm giving a bit leeway on the activities that allocate memory, since 
most of the time it's just manipulation of some data structure in 
memory. Granted, it might cause hard-disk activity every once in a 
while for thrashing, but even simple memory access could cause this 
too. Also, note that the restriction is tight on some platforms but not 
so tight on others. I was hoping at least this would work on these not 
so stringent systems. However, I think invoking system calls that block 
the callback for possibly unspecified amount of time is the forbidden 
game.

I think garbage collection inside the callback is probably okay, if it 
doesn't do other fancy things, such as dispatching signals or influence 
thread scheduling. What does O'Caml runtime do during garbage 
collection?

> - Event loops (register Caml callbacks, then enter a library-provider 
> event
>   handler that will block and invoke the callbacks one at a time,
>   but not from a signal or interrupt context).

That's also a possibility; does it play well with O'Caml Threads?

Thanks for the response.

liulk

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners