This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of Resolved status.
Section: 126.96.36.199.3 [istream.extractors] Status: Resolved Submitter: Richard Smith Opened: 2015-05-08 Last modified: 2018-11-13
View all other issues in [istream.extractors].
View all issues with Resolved status.
We removed gets() (due to an NB comment and C11 — bastion of backwards compatibility — doing the same). Should we remove this too?Unlike gets(), there are legitimate uses:
char buffer; char text = // ... ostream_for_buffer(text) >> buffer; // ok, can't overrun buffer
… but the risk from constructs like "std::cin >> buffer" seems to outweigh the benefit.The issue had been discussed on the library reflector starting around c++std-lib-35541.
VV: Request a paper to deprecate / remove anything
[2015-10, Kona Saturday afternoon]
STL: This overload is evil and should probably die.
VV: I agree with that, even though I don't care.
STL: Say that we either remove it outright following the gets() rationale, or at least deprecate it.
Move to Open; needs a paper.
[2016-08, Chicago: Zhihao Yuan comments and provides wording]
I would like to keep some reasonable code working;
Reasonable code includes two cases:
width() > 0, any pointer argument
width() >= 0, array argument
For a), banning bad code will become a silent behavior change at runtime; for b), it breaks at compile time.
I propose to replace these signatures with references to arrays. An implementation may want to ship the old instantiatations in the binary without exposing the old signatures.
Tues PM: General agreement on deprecating the unsafe call, but no consensus for the P/R.
General feeling that implementation experience would be useful.
[2018-08-23 Batavia Issues processing]
Will be resolved by the adoption of P0487.
[2018-11-11 Resolved by P0487R1, adopted in San Diego.]
This wording is relative to N4606.
Modify 188.8.131.52.3 [istream.extractors] as indicated:
template<class charT, class traits> basic_istream<charT, traits>& operator>>(basic_istream<charT, traits>& in,
charT* s); template<class traits> basic_istream<char, traits>& operator>>(basic_istream<char, traits>& in, unsigned char* s); template<class traits> basic_istream<char, traits>& operator>>(basic_istream<char, traits>& in, signed char* s);
-7- Effects: Behaves like a formatted input member (as described in 184.108.40.206.1 [istream.formatted.reqmts]) of in. After a sentry object is constructed, operator>> extracts characters and stores them into
successive locations of an array whose first element is designated bys. If width() is greater than zero, n is width(). Otherwise n is the number of elements of the largest array of char_type that can store a terminating charT(). n is the maximum number of characters stored.