On Thu, 2 Dec 2004, Bob Jamison wrote:
Jon A. Cruz wrote:
Seriously, though, there are some issues I have with things. Some is the 'built-in' localization in streams. Generally good for the first 80% of a project, but breaks down in the final 20%. Same with printf.
Well, I'm not saying that the plain vanilla iostream or fstream packages are great, either. What we can do, though, is create our own classes that implement istream and ostream, but have the features that we need. For example, your Win9x fix for the WinAPI's incorrect mapping of fopen() can be wrapped in iostreams. And we can use the wonderful Glib::ustring for a nice stringstream. What we get by using the interfaces is the ability to extend/specialize then, and daisy-chain them together, pipe them, etc.
Can you show us an example of the before/after code? I'm curious what the existing code looks like, and how it'll get streamlined with the new stuff.
Also, take a look at my ftos code - this was written as a part of a iostream subclassing thing I did, and worked pretty good. I'd love to see this incorporated since it provides a better approach to formatting numbers (so you can say x="4.21" instead of x="4.209999999").
Bryce