Rainer Orth <[email protected]> wrote: > > That way, a library could be "ready" for threads if the containing > > application actually used threads, and still work fine if the parent > > didn't. If you were building such a shared library, you'd want -G but > > you would *not* want automatic binding with any threads library, because > > that's something for the main application to decide. > > ... though you'd have been able to decide that by compiling with -mt > (which would define -D_REENTRANT as required), but *not* linking with it.
Since MT was introduced more than 20 years ago, there was always a distinction betweem "mt aware" and "mt hot". An "mt aware" lib does not need to enforce mt but it must permit mt hot applications to work correctly. Jörg -- EMail:[email protected] (home) Jörg Schilling D-13353 Berlin [email protected] (uni) [email protected] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily _______________________________________________ tools-compilers mailing list [email protected]
