Thanks for the guidelines, Robin. I guess no one has
any hard rules on which calls are safe and which
aren't.
While I'm on the subject, does anyone have a trick or
method they use to keep their thread-safe code
separate from the non-thread-safe? i.e. I make a
conscious effort to put "Thread" in a function name if
it gets launched as a background thread, but I'll be
the first to admit that my organization stops there.
If those background threads call another function, I'm
in no position to know for a fact whether that
function can run legally in a background thread.
I guess the only solution to this danger is a
programmer's self control (which I seem to lack), so
how do you guys keep from falling into the sloppy-code
trap here?
Gre7g
ยทยทยท
____________________________________________________________________________________
Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center.
http://autos.yahoo.com/green_center/