On Thu, 4 Dec 1997, Dale Martin wrote: > "Orn E. Hansen" <[EMAIL PROTECTED]> writes: > > If you have to remove all the classes in c++ to get threads working, > > there isn't much sense in using c++ :-) > > > > I've had the same problem, and as far as I've been able to collect, > > g++ simply isn't, and won't be thread safe. If you wish for a thread > > safe environment, get stdc++ 2.8.0 or the 'egcs' compiler. > > Thanks for the reply, and for confirming what I suspected.
AFAIK, in EGCS libstdc++: - I/O is 99% thread safe. - SGI STL claimed to be thread safe - small stuff like complex etc is thread safe - string classes probably are thread unsafe > For what it's worth, I downloaded and compiled egcs-1.0 this morning and it > works fine on my code. (I configured it with -enable-threads - I assume > this is necessary for it to produce thread safe code.) --enable-threads enables thread support in ObjC run-time library, libobjc.a. > Later, > Dale regards OK -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .