This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of TC1 status.
Section: 31.7.5.3.3 [istream.extractors] Status: TC1 Submitter: Angelika Langer Opened: 1998-07-14 Last modified: 2017-04-22
Priority: Not Prioritized
View all other issues in [istream.extractors].
View all issues with TC1 status.
Discussion:
Extractors for char* (27.6.1.2.3) do not store a null character after the extracted character sequence whereas the unformatted functions like get() do. Why is this?
Comment from Jerry Schwarz: There is apparently an editing glitch. You'll notice that the last item of the list of what stops extraction doesn't make any sense. It was supposed to be the line that said a null is stored.
Proposed resolution:
[istream::extractors], paragraph 7, change the last list item from:
A null byte (
charT()) in the next position, which may be the first position if no characters were extracted.
to become a new paragraph which reads:
Operator>> then stores a null byte (
charT()) in the next position, which may be the first position if no characters were extracted.