This is the mail archive of the libstdc++@sourceware.cygnus.com mailing list for the libstdc++ project. See the libstdc++ home page for more information.
Benjamin Kosnik wrote: > What works: (noted with the chapter # of the ISO-14882 standard) > ----------- > - exceptions, op new etc. (18, 19) > - SGI-STL release 3.12 utilities, containers, algorithms, and iterators. > (20,23,24,25), and ostreambuf_iterator<>. Plus fixes for auto_ptr, > and an interator class for vector and string. > - basic_string<> (21) > - locale, some facets (ctype, num_put, collate), stubs for the rest. (22) > - Gabriel dos Reis's valarray<>, and Drepper's complex<>. (However, > note that numeric_limits<> is not tailored for your target. You > must do that by hand.) (26) > - ios_base, basic_ios<>, basic_streambuf<>, basic_stringbuf<>, > basic_filebuf<>, ostream<>, operator<< for integers, strings. (27) > > What doesn't: > ------------- > - too many parts of istream, op>>, op<<(double&) etc. (27) > - Most facet implementations are stubs. (22) > - Almost no optimizations for small-footprint/low-overhead. (22,27) > - It has not been fully audited for standard conformance in the areas > that do work--check out the testsuite directory for an idea of the > limitations of the current implementation. > - It has not been made thread-safe. > - There has been some work to wrap the C headers in namespace std::, but > it may not be complete yet, and C macros are not shadowed. Please consult > the mailing list archives for more information. It looks like most things are implemented. Is there a chance that it will be ready in time for egcs 1.2? That would be really really nice. Also do you know when you plan on merging libstdc++ in with the rest of the egcs tree? -- Kevin Atkinson kevinatk@home.com http://metalab.unc.edu/kevina/