As you say, that only used to be a problem in stdlib, it is no longer a problem.
There are various features of std::string not present in GooString, which I need for my patches to poppler. Most obviously, it is missing a substr() member. Are there any restrictions/problems with the current std::string when compared with GooString? > As far as presence of GooString in public API is concerned, I guess it comes > from the fact (or FUD otherwise) that putting template C++ classes in public > API is considered ABI-unsafe (easier to break). And while there aren't any > issues with STL in this regard recently, Boost for instance would be a > different story. > So GooString would be safe alternative. > > regards > MM > _______________________________________________ poppler mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/poppler
