>As for atomicity.h, there are two non-mutually-exclusive alternatives: >>Ranjit's patch: http://gcc.gnu.org/ml/libstdc++/2002-12/msg00232.html >Phil's patch: http://gcc.gnu.org/ml/libstdc++/2003-01/msg00278.html Phil's patch (or a variant thereof) went in today apparently: http://gcc.gnu.org/ml/libstdc++/2003-02/msg00331.html One down. One to go. Are the GCC elves working behind the scenes? >Is this splitting off feasible given the timeline of the GCC 3.3 >release or is a quick fix perhaps warranted? Shall I take a swipe at busting the network code into POSIX and Win32 implementations, since people seem to think that this is the least worst solution? Is anyone working on this? Anyone? -- Mohan http://www.thisiscool.com/ http://www.animalsong.org/