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 33,247 of 33,346    |
|    Daryle Walker to All    |
|    What's the history of pbackfail (so I co    |
|    15 Oct 13 22:40:53    |
      From: darylew@googlemail.com              I'm thinking of making a stream based off a read-only sequence. Only       one of the read methods of basic_streambuf may write: pbackfail. This       method gets called for two reasons: (1) the stream-buffer is already at       the first input position or (2) the character to be written back differs       from what's already there. It's a good thing that stream-buffer stops       before writing a different character, otherwise I'll be screwed using an       actually-immutable backing sequence (with const_cast). Who came up with       that policy? Was it from someone who had the same use-case I have?              (And did six different people come up with the method names? Does the       public method have the prefix, or its protected virtual helper, or both?       Which prefixes should be used? Which suffixes, if any, should be used?       How did some public/protected method pairs go without a common base-word?)              Daryle W.                     --        [ 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