home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.lang.c++.moderated      Moderated discussion of C++ superhackery      33,346 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 32,840 of 33,346   
   Edward Rosten to Seungbeom Kim   
   Re: iostream replacement   
   30 Jan 13 09:00:29   
   
   From: firstname.dot.lastname@googlemail.com   
      
   On Mon, 28 Jan 2013 23:30:55 -0600, Seungbeom Kim wrote:   
      
   > You have been lucky since you didn't need to print size_t or such. :)   
   >   
   >   
   > The "effective type-safety" you mention can help in some situations, but   
   > it cannot ensure portable type-safety. And I'm pretty sure that using   
   > the stream interface would have saved us a lot of trouble.   
      
   Certainly: I'm merely attempting to explain the continued popularity of   
   printf. It's a combination of nice syntax plus just about enough compiler   
   support to prevent it from being a total nightmare. The new putf()   
   proposal (mentioned elsewhere in the thread) seems very nice in that it   
   generally appears to have the nice syntax, proper interoperability with   
   ostreams and generally does what one would expect.   
      
   Personally, I don't use genuine printf, but one of the type safe   
   replacements instead.   
      
      
   -Ed   
      
      
   --   
         [ 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)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca