1*404b540aSrobert2003-04-26 2*404b540aSrobert 3*404b540aSrobert- _GLIBCPP_HAS_BUILTIN_SINF: We should still hold out for a cleaner solution the is currenly the case in bits/std_cmath.h. 4*404b540aSrobert 5*404b540aSrobert- there may be one set of remaining string bugs, dependent on final 6*404b540aSrobertclarification of the string::find technicalities when finding in an 7*404b540aSrobertempty string or using an empty string for an argument. At the very 8*404b540aSrobertleast, v-3 has interpreted the standard in a way that is in opposition 9*404b540aSrobertto other libraries on other platforms. 10*404b540aSrobert 11*404b540aSrobert- trigraphs and keywords a la the iso646 header are not correctly 12*404b540aSrobertimplemented. It looks like the compiler recognizes them as keywords 13*404b540aSrobertbut then doesn't translate into the correct bit ops. It is a mystery. 14*404b540aSrobert 15*404b540aSrobert- wide strings have not been tested, and may therefore be unusable. 16*404b540aSrobert 17*404b540aSrobert- Chapter 27 io functionality is not finished. As such, there are 18*404b540aSrobertknown bugs in: filebuf::putbackfail 19*404b540aSrobert 20*404b540aSrobert- Many facet implementations are stubs. (22) 21*404b540aSrobert 22*404b540aSrobert- Almost no optimizations for small-footprint/low-overhead. (22,27) 23*404b540aSrobert 24*404b540aSrobert- There has been some work to wrap the C headers in namespace std::, but 25*404b540aSrobert it may not be complete yet, and C macros are not shadowed. Please consult 26*404b540aSrobert the mailing list archives for more information. 27*404b540aSrobert 28*404b540aSrobert 29