Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c++ > #5189
| From | Pete Becker <pete@versatilecoding.com> |
|---|---|
| Organization | Roundhouse Consulting, Ltd. |
| Newsgroups | comp.lang.c++ |
| Date | 2011-05-19 18:11 -0400 |
| Message-ID | <201105191811177950-pete@versatilecodingcom> (permalink) |
| References | <ostream-20110519004001@ram.dialup.fu-berlin.de> <ir420o$6kt$1@online.de> |
| Subject | Re: ::std::ostream << char |
On 2011-05-19 17:27:52 -0400, Björn said: > Alf P. Steinbach /Usenet wrote: > >> * Stefan Ram, on 19.05.2011 00:54: >>> The output operator "<<" for operands of type »::std::ostream« and >>> »char« (in this order) seems to be defined as a non-member, while >>> for »double« it seems to be defined as a member. >> >> This may depend on which standard you're talking about. I haven't >> checked but as I recall some of the issues related to this were >> fixed in C++0x. Which is on its way Real Soon Now. > > In the current draft N3242 from 2011-02-28 it is still as described. Yes, that hasn't been changed. -- Pete Roundhouse Consulting, Ltd. (www.versatilecoding.com) Author of "The Standard C++ Library Extensions: a Tutorial and Reference (www.petebecker.com/tr1book)
Back to comp.lang.c++ | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: ::std::ostream << char "Alf P. Steinbach /Usenet" <alf.p.steinbach+usenet@gmail.com> - 2011-05-19 01:39 +0200
Re: ::std::ostream << char Björn <hen03@nurfuerspam.de> - 2011-05-19 23:27 +0200
Re: ::std::ostream << char Pete Becker <pete@versatilecoding.com> - 2011-05-19 18:11 -0400
csiph-web