From: mel@zzzzz.invalid   
      
   On Thu, 24 Jan 2013 23:59:38 -0800 (PST)   
   fmatthew5876  wrote:   
      
   >   
   > Have there ever been any proposals are serious talks about a   
   > replacement for the iostreams library? Many people including myself   
   > vehemently dislike this library.   
      
   I like it ;)   
      
    Among other things, its painfully   
   > slow, overly verbose, and is the first example of operator   
   > overloading abuse.   
      
   Couldn't agree. I used it for my serialization library for years,   
   and didn't found any problems with it. Why do you think is slow?   
      
    It also separates formatting from the data. Have   
   > you ever tried to print a hex byte with iostreams? Its really ugly.   
      
   Yes. iostreams formatting is pain, I agree.   
      
   >   
   > Printf while not typesafe, is much more convenient, efficient, easier   
   > to use, and supports multilingual applications better. With variadic   
   > templates there are now even examples of typesafe printf.   
      
   I use both printf (for complex formating) and iostreams.   
   There is no problem now to provide type safe printf, but please don;t   
   take away streams as they are really useful now.   
      
   --   
   drwxr-xr-x 2 bmaxa bmaxa 4096 Jan 28 05:40 .   
      
      
         [ See http://www.gotw.ca/resources/clcm.htm for info about ]   
         [ comp.lang.c++.moderated.    First time posters: Do this! ]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)