Reference ISO/IEC IS 14882:1998(E)
This document is the Index by Section for the Library Active Issues List, Library Defect Reports List, and Library Closed Issues List.
Also see:
Section | Issue | Title | Status |
3.6.3 | 462 | Destroying objects with static storage duration | New |
17 | 182 | Ambiguous references to size_t | WP |
17 | 230 | Assignable specified without also specifying CopyConstructible | WP |
17 | 336 | Clause 17 lack of references to deprecated headers | WP |
17 | 385 | Does call by value imply the CopyConstructible requirement? | Open |
17.3.1.1 | 424 | normative notes | Open |
17.3.1.3 | 222 | Are throw clauses necessary if a throw is already implied by the effects clause? | TC |
17.3.2.1.2 | 262 | Bitmask operator ~ specified incorrectly | WP |
17.3.2.1.2 | 339 | definition of bitmask type restricted to clause 27 | WP |
17.4.1.1 | 229 | Unqualified references of other library entities | WP |
17.4.1.1 | 350 | allocator<>::address | NAD Future |
17.4.1.2 | 310 | Is errno a macro? | WP |
17.4.1.2 | 456 | Traditional C header files are overspecified | Open |
17.4.1.2 | 465 | Contents of <ciso646> | New |
17.4.2.2 | 1 | C library linkage editing oversight | TC |
17.4.3.1 | 120 | Can an implementor add specializations? | WP |
17.4.3.1 | 226 | User supplied specializations or overloads of namespace std function templates | WP |
17.4.3.1 | 232 | "depends" poorly defined in 17.4.3.1 | WP |
17.4.3.1 | 422 | explicit specializations of member functions of class templates | Open |
17.4.3.1.1 | 294 | User defined macros and standard headers | Open |
17.4.3.4 | 404 | May a replacement allocation function be declared inline? | WP |
17.4.4 | 94 | May library implementors add template parameters to Standard Library classes? | NAD |
17.4.4.3 | 147 | Library Intro refers to global functions that aren't global | TC |
17.4.4.3 | 225 | std:: algorithms use of other unqualified algorithms | WP |
17.4.4.4 | 95 | Members added by the implementation | NAD |
17.4.4.8 | 119 | Should virtual functions be allowed to strengthen the exception specification? | TC |
17.4.4.8 | 372 | Inconsistent description of stdlib exceptions | NAD |
18.1 | 306 | offsetof macro and non-POD types | WP |
18.1 | 449 | Library Issue 306 Goes Too Far | Ready |
18.2.1 | 201 | Numeric limits terminology wrong | Open |
18.2.1.2 | 205 | numeric_limits unclear on how to determine floating point types | NAD |
18.2.1.5 | 184 | numeric_limits<bool> wording problems | WP |
18.2.2 | 416 | definitions of XXX_MIN and XXX_MAX macros in climits | Open |
18.3 | 3 | Atexit registration during atexit() call is not described | TC |
18.3 | 462 | Destroying objects with static storage duration | New |
18.4.1 | 9 | Operator new(0) calls should not yield the same pointer | TC |
18.4.1 | 404 | May a replacement allocation function be declared inline? | WP |
18.4.1.1 | 206 | operator new(size_t, nothrow) may become unlinked to ordinary operator new if ordinary version replaced | NAD |
18.4.1.1 | 319 | Storage allocation wording confuses "Required behavior", "Requires" | WP |
18.4.1.2 | 298 | ::operator delete[] requirement incorrect/insufficient | WP |
18.4.1.2 | 319 | Storage allocation wording confuses "Required behavior", "Requires" | WP |
18.4.1.3 | 114 | Placement forms example in error twice | TC |
18.4.1.3 | 196 | Placement new example has alignment problems | Dup |
18.6 | 70 | Uncaught_exception() missing throw() specification | TC |
18.6.1 | 108 | Lifetime of exception::what() return unspecified | TC |
18.6.1 | 372 | Inconsistent description of stdlib exceptions | NAD |
18.6.1 | 471 | result of what() implementation-defined | New |
18.6.2.1 | 266 | bad_exception::~bad_exception() missing Effects clause | WP |
18.6.2.4 | 433 | Contradiction in specification of unexpected() | NAD |
18.6.3.3 | 313 | set_terminate and set_unexpected question | NAD |
18.6.3.3 | 314 | Is the stack unwound when terminate() is called? | NAD |
18.6.4 | 70 | Uncaught_exception() missing throw() specification | TC |
18.7 | 269 | cstdarg and unnamed parameters | NAD |
19.1 | 254 | Exception types in clause 19 are constructed from std::string | Open |
19.3 | 288 | <cerrno> requirements missing macro EILSEQ | WP |
19.3 | 310 | Is errno a macro? | WP |
20 | 312 | Table 27 is missing headers | WP |
20.1.3 | 390 | CopyConstructible requirements too strict | NAD Future |
20.1.5 | 12 | Way objects hold allocators unclear | NAD |
20.1.5 | 197 | max_size() underspecified | Open |
20.1.5 | 199 | What does allocate(0) return? | TC |
20.1.5 | 258 | Missing allocator requirement | Open |
20.1.5 | 274 | a missing/impossible allocator requirement | WP |
20.1.5 | 277 | Normative encouragement in allocator requirements unclear | NAD |
20.1.5 | 350 | allocator<>::address | NAD Future |
20.1.5 | 401 | incorrect type casts in table 32 in lib.allocator.requirements | Open |
20.1.5 | 402 | wrong new expression in [some_]allocator::construct | WP |
20.1.5 | 431 | Swapping containers with unequal allocators | Open |
20.2.2 | 181 | make_pair() unintended behavior | TC |
20.2.2 | 265 | std::pair::pair() effects overly restrictive | WP |
20.2.2 | 296 | Missing descriptions and requirements of pair operators | NAD |
20.2.2 | 348 | Minor issue with std::pair operator< | NAD Future |
20.2.2 | 353 | std::pair missing template assignment | NAD Future |
20.3 | 185 | Questionable use of term "inline" | WP |
20.3 | 351 | unary_negate and binary_negate: struct or class? | NAD |
20.3.1 | 257 | STL functional object and iterator inheritance. | NAD |
20.3.1 | 480 | unary_function and binary_function should have protected nonvirtual destructors | New |
20.3.6 | 109 | Missing binders for non-const sequence elements | WP |
20.3.6.2 | 362 | bind1st/bind2nd type safety | Open |
20.3.7 | 284 | unportable example in 20.3.7, p6 | WP |
20.3.8 | 297 | const_mem_fun_t<>::argument_type should be const T* | WP |
20.4.1.1 | 234 | Typos in allocator definition | WP |
20.4.1.1 | 350 | allocator<>::address | NAD Future |
20.4.1.1 | 400 | redundant type cast in lib.allocator.members | WP |
20.4.1.1 | 402 | wrong new expression in [some_]allocator::construct | WP |
20.4.3 | 425 | return value of std::get_temporary_buffer | Ready |
20.4.5 | 127 | auto_ptr<> conversion issues | TC |
20.4.5 | 249 | Return Type of auto_ptr::operator= | NAD |
20.4.5 | 463 | auto_ptr usability issues | New |
20.4.5.3 | 2 | Auto_ptr conversions effects incorrect | NAD |
21 | 7 | String clause minor problems | TC |
21 | 85 | String char types | NAD |
21 | 343 | Unspecified library header dependencies | NAD Future |
21.1.1 | 335 | minor issue with char_traits, table 37 | WP |
21.1.2 | 352 | missing fpos requirements | WP |
21.1.3.1 | 467 | char_traits::lt(), compare(), and memcmp() | New |
21.1.3.2 | 57 | Mistake in char_traits | TC |
21.3 | 4 | Basic_string size_type and difference_type should be implementation defined | NAD |
21.3 | 42 | String ctors specify wrong default allocator | TC |
21.3 | 83 | String::npos vs. string::max_size() | TC |
21.3 | 209 | basic_string declarations inconsistent | TC |
21.3 | 263 | Severe restriction on basic_string reference counting | WP |
21.3.1 | 86 | String constructors don't describe exceptions | TC |
21.3.1 | 301 | basic_string template ctor effects clause omits allocator argument | WP |
21.3.1 | 466 | basic_string ctor should prevent null pointer error | New |
21.3.4 | 104 | Description of basic_string::operator[] is unclear | NAD |
21.3.4 | 259 | basic_string::operator[] and const correctness | WP |
21.3.5 | 84 | Ambiguity with string::insert() | NAD |
21.3.5.2 | 88 | Inconsistency between string::insert() and string::append() | NAD |
21.3.5.4 | 88 | Inconsistency between string::insert() and string::append() | NAD |
21.3.5.4 | 89 | Missing throw specification for string::insert() and string::replace() | Dup |
21.3.5.4 | 377 | basic_string::insert and length_error | NAD |
21.3.5.5 | 27 | String::erase(range) yields wrong iterator | TC |
21.3.5.5 | 428 | string::erase(iterator) validity | WP |
21.3.5.6 | 89 | Missing throw specification for string::insert() and string::replace() | Dup |
21.3.5.6 | 368 | basic_string::replace has two "Throws" paragraphs | Open |
21.3.5.8 | 403 | basic_string::swap should not throw exceptions | WP |
21.3.6.4 | 141 | basic_string::find_last_of, find_last_not_of say pos instead of xpos | TC |
21.3.6.6 | 141 | basic_string::find_last_of, find_last_not_of say pos instead of xpos | TC |
21.3.6.8 | 5 | String::compare specification questionable | TC |
21.3.6.8 | 87 | Error in description of string::compare() | Dup |
21.3.7.9 | 25 | String operator<< uses width() value wrong | TC |
21.3.7.9 | 67 | Setw useless for strings | Dup |
21.3.7.9 | 90 | Incorrect description of operator >> for strings | TC |
21.3.7.9 | 91 | Description of operator>> and getline() for string<> might cause endless loop | WP |
21.3.7.9 | 211 | operator>>(istream&, string&) doesn't set failbit | TC |
21.3.7.9 | 435 | bug in DR 25 | Ready |
21.4 | 345 | type tm in <cwchar> | WP |
22 | 317 | Instantiation vs. specialization of facets | WP |
22.1.1 | 31 | Immutable locale values | TC |
22.1.1 | 37 | Leftover "global" reference | TC |
22.1.1 | 137 | Do use_facet and has_facet look in the global locale? | TC |
22.1.1 | 268 | Typo in locale synopsis | WP |
22.1.1 | 330 | Misleading "exposition only" value in class locale definition | NAD |
22.1.1 | 360 | locale mandates inefficient implementation | WP |
22.1.1 | 378 | locale immutability and locale::operator=() | Review |
22.1.1.1.1 | 21 | Codecvt_byname<> instantiations | TC |
22.1.1.1.1 | 30 | Wrong header for LC_* | TC |
22.1.1.1.1 | 121 | Detailed definition for ctype<wchar_t> specialization | NAD |
22.1.1.1.1 | 327 | Typo in time_get facet in table 52 | WP |
22.1.1.1.1 | 340 | interpretation of has_facet<Facet>(loc) | WP |
22.1.1.1.1 | 347 | locale::category and bitmask requirements | WP |
22.1.1.1.1 | 447 | Wrong template argument for time facets | Dup |
22.1.1.1.2 | 436 | are cv-qualified facet types valid facets? | WP |
22.1.1.3 | 14 | Locale::combine should be const | TC |
22.1.1.3 | 15 | Locale::name requirement inconsistent | TC |
22.1.1.3 | 452 | locale::combine should be permitted to generate a named locale | Review |
22.1.1.5 | 8 | Locale::global lacks guarantee | TC |
22.1.2 | 38 | Facet definition incomplete | TC |
22.1.3.2 | 391 | non-member functions specified as const | WP |
22.2 | 228 | Incorrect specification of "..._byname" facets | WP |
22.2 | 338 | is whitespace allowed between `-' and a digit? | WP |
22.2 | 439 | Should facets be copyable? | NAD |
22.2.1 | 339 | definition of bitmask type restricted to clause 27 | WP |
22.2.1 | 356 | Meaning of ctype_base::mask enumerators | Open |
22.2.1.1 | 473 | underspecified ctype calls | New |
22.2.1.1.2 | 126 | typos in Effects clause of ctype::do_narrow() | TC |
22.2.1.1.2 | 152 | Typo in scan_is() semantics | TC |
22.2.1.1.2 | 379 | nonsensical ctype::do_widen() requirement | WP |
22.2.1.1.2 | 417 | what does ctype::do_widen() return on failure | Open |
22.2.1.2 | 124 | ctype_byname<charT>::do_scan_is & do_scan_not return type should be const charT* | TC |
22.2.1.3.2 | 28 | Ctype<char>is ambiguous | TC |
22.2.1.3.2 | 153 | Typo in narrow() semantics | WP |
22.2.1.3.2 | 207 | ctype<char> members return clause incomplete | Dup |
22.2.1.3.2 | 236 | ctype<char>::is() member modifies facet | Dup |
22.2.1.4 | 16 | Bad ctype_byname<char> decl | TC |
22.2.1.4 | 138 | Class ctype_byname<char> redundant and misleading | NAD Future |
22.2.1.5 | 72 | Do_convert phantom member function | Dup |
22.2.1.5 | 75 | Contradiction in codecvt::length's argument types | TC |
22.2.1.5 | 76 | Can a codecvt facet always convert one internal character at a time? | WP |
22.2.1.5 | 382 | codecvt do_in/out result | Open |
22.2.1.5.2 | 10 | Codecvt<>::do unclear | Dup |
22.2.1.5.2 | 19 | "Noconv" definition too vague | TC |
22.2.1.5.2 | 24 | "do_convert" doesn't exist | TC |
22.2.1.5.2 | 33 | Codecvt<> mentions from_type | TC |
22.2.1.5.2 | 43 | Locale table correction | Dup |
22.2.1.5.2 | 74 | Garbled text for codecvt::do_max_length | TC |
22.2.1.5.2 | 302 | Need error indication from codecvt<>::do_length | NAD |
22.2.1.5.2 | 305 | Default behavior of codecvt<wchar_t, char, mbstate_t>::length() | WP |
22.2.1.5.2 | 380 | typos in codecvt tables 53 and 54 | WP |
22.2.1.5.2 | 381 | detection of invalid mbstate_t in codecvt | WP |
22.2.2 | 344 | grouping + showbase | NAD |
22.2.2.1.1 | 18 | Get(...bool&) omitted | TC |
22.2.2.1.1 | 275 | Wrong type in num_get::get() overloads | WP |
22.2.2.1.2 | 17 | Bad bool parsing | TC |
22.2.2.1.2 | 23 | Num_get overflow result | Open |
22.2.2.1.2 | 154 | Missing double specifier for do_get() | TC |
22.2.2.1.2 | 221 | num_get<>::do_get stage 2 processing broken | WP |
22.2.2.1.2 | 321 | Typo in num_get | WP |
22.2.2.1.2 | 358 | interpreting thousands_sep after a decimal_point | WP |
22.2.2.1.2 | 427 | stage 2 and rationale of DR 221 | Open |
22.2.2.1.2 | 459 | Requirement for widening in stage 2 is overspecification | Open |
22.2.2.2.1 | 359 | num_put<>::do_put (..., bool) undocumented | WP |
22.2.2.2.2 | 34 | True/falsename() not in ctype<> | TC |
22.2.2.2.2 | 231 | Precision in iostream? | WP |
22.2.2.2.2 | 282 | What types does numpunct grouping refer to? | WP |
22.2.2.2.2 | 361 | num_get<>::do_get (..., void*&) checks grouping | NAD |
22.2.3.1.2 | 20 | Thousands_sep returns wrong type | TC |
22.2.3.2 | 318 | Misleading comment in definition of numpunct_byname | WP |
22.2.5 | 248 | time_get fails to set eofbit | WP |
22.2.5.1 | 71 | Do_get_monthname synopsis missing argument | TC |
22.2.5.1 | 461 | time_get hard or impossible to implement | New |
22.2.5.3.2 | 164 | do_put() has apparently unused fill argument | TC |
22.2.6.2.2 | 328 | Bad sprintf format modifier in money_put<>::do_put() | WP |
22.2.6.3.1 | 374 | moneypunct::frac_digits returns int not unsigned | NAD |
22.2.6.3.2 | 325 | Misleading text in moneypunct<>::do_grouping | WP |
22.2.6.3.2 | 374 | moneypunct::frac_digits returns int not unsigned | NAD |
22.2.6.4 | 326 | Missing typedef in moneypunct_byname | NAD |
22.2.8 | 40 | Meaningless normative paragraph in examples | TC |
22.2.8 | 148 | Functions in the example facet BoolNames should be const | TC |
22.2.8 | 217 | Facets example (Classifying Japanese characters) contains errors | TC |
23 | 97 | Insert inconsistent definition | NAD |
23 | 180 | Container member iterator arguments constness has unintended consequences | NAD Future |
23 | 343 | Unspecified library header dependencies | NAD Future |
23 | 470 | accessing containers from their elements' special functions | New |
23.1 | 51 | Requirement to not invalidate iterators missing | TC |
23.1 | 179 | Comparison of const_iterators to iterators doesn't work | WP |
23.1 | 197 | max_size() underspecified | Open |
23.1 | 276 | Assignable requirement for container value type overly strict | WP |
23.1 | 279 | const and non-const iterators should have equivalent typedefs | NAD |
23.1 | 322 | iterator and const_iterator should have the same value type | WP |
23.1 | 371 | Stability of multiset and multimap member functions | Open |
23.1 | 446 | Iterator equality between different containers | Open |
23.1 | 479 | Container requirements and placement new | New |
23.1.1 | 130 | Return type of container::erase(iterator) differs for associative containers | Review |
23.1.1 | 139 | Optional sequence operation table description unclear | TC |
23.1.1 | 149 | Insert should return iterator to first element inserted | NAD Future |
23.1.1 | 151 | Can't currently clear() empty container | TC |
23.1.1 | 355 | Operational semantics for a.back() | WP |
23.1.1 | 438 | Ambiguity in the "do the right thing" clause | Review |
23.1.2 | 82 | Missing constant for set elements | NAD |
23.1.2 | 102 | Bug in insert range in associative containers | Dup |
23.1.2 | 103 | set::iterator is required to be modifiable, but this allows modification of keys | WP |
23.1.2 | 130 | Return type of container::erase(iterator) differs for associative containers | Review |
23.1.2 | 192 | a.insert(p,t) is inefficient and overconstrained | NAD |
23.1.2 | 215 | Can a map's key_type be const? | NAD |
23.1.2 | 224 | clear() complexity for associative containers refers to undefined N | TC |
23.1.2 | 233 | Insertion hints in associative containers | Open |
23.1.2 | 246 | a.insert(p,t) is incorrectly specified | Dup |
23.1.2 | 264 | Associative container insert(i, j) complexity requirements are not feasible. | WP |
23.1.2 | 316 | Vague text in Table 69 | WP |
23.1.2 | 354 | Associative container lower/upper bound requirements | WP |
23.1.2 | 451 | Associative erase should return an iterator | Dup |
23.2.1 | 101 | No way to free storage for vector and deque | NAD |
23.2.1.1 | 144 | Deque constructor complexity wrong | TC |
23.2.2.1 | 237 | Undefined expression in complexity specification | WP |
23.2.2.1 | 320 | list::assign overspecified | WP |
23.2.2.2 | 132 | list::resize description uses random access iterators | TC |
23.2.2.4 | 131 | list::splice throws nothing | NAD |
23.2.2.4 | 250 | splicing invalidates iterators | WP |
23.2.2.4 | 278 | What does iterator validity mean? | WP |
23.2.2.4 | 300 | list::merge() specification incomplete | WP |
23.2.2.4 | 315 | Bad "range" in list::unique complexity | WP |
23.2.3 | 307 | Lack of reference typedefs in container adaptors | WP |
23.2.3.1 | 410 | Missing semantics for stack and queue comparison operators | Ready |
23.2.3.3 | 410 | Missing semantics for stack and queue comparison operators | Ready |
23.2.4 | 69 | Must elements of a vector be contiguous? | TC |
23.2.4 | 101 | No way to free storage for vector and deque | NAD |
23.2.4 | 464 | Suggestion for new member functions in standard containers | New |
23.2.4.1 | 134 | vector constructors over specified | TC |
23.2.4.2 | 329 | vector capacity, reserve and reallocation | WP |
23.2.4.2 | 341 | Vector reallocation and swap | WP |
23.2.4.3 | 247 | vector, deque::insert complexity | Open |
23.2.4.3 | 329 | vector capacity, reserve and reallocation | WP |
23.2.4.3 | 406 | vector::insert(s) exception safety | Review |
23.2.4.3 | 414 | Which iterators are invalidated by v.erase()? | WP |
23.2.5 | 96 | Vector<bool> is not a container | Open |
23.2.5 | 469 | vector<bool> ill-formed relational operators | New |
23.3 | 451 | Associative erase should return an iterator | Dup |
23.3.1 | 133 | map missing get_allocator() | TC |
23.3.1 | 140 | map<Key, T>::value_type does not satisfy the assignable requirement | NAD Future |
23.3.1 | 464 | Suggestion for new member functions in standard containers | New |
23.3.1.2 | 334 | map::operator[] specification forces inefficient implementation | WP |
23.3.3 | 214 | set::find() missing const overload | WP |
23.3.3 | 450 | set::find is inconsistent with associative container requirements | Dup |
23.3.4 | 214 | set::find() missing const overload | WP |
23.3.5 | 11 | Bitset minor problems | TC |
23.3.5 | 116 | bitset cannot be constructed with a const char* | NAD Future |
23.3.5.1 | 396 | what are characters zero and one | Open |
23.3.5.1 | 457 | bitset constructor: incorrect number of initialized bits | Review |
23.3.5.2 | 186 | bitset::set() second parameter should be bool | WP |
23.3.5.2 | 434 | bitset::to_string() hard to use | Review |
23.3.5.3 | 303 | Bitset input operator underspecified | WP |
24.1 | 198 | Validity of pointers and references unspecified after iterator destruction | WP |
24.1 | 208 | Unnecessary restriction on past-the-end iterators | TC |
24.1 | 304 | Must *a return an lvalue when a is an input iterator? | NAD |
24.1 | 346 | Some iterator member functions should be const | WP |
24.1 | 407 | Can singular iterators be destroyed? | WP |
24.1 | 408 | Is vector<reverse_iterator<char*> > forbidden? | Open |
24.1 | 446 | Iterator equality between different containers | Open |
24.1.1 | 98 | Input iterator requirements are badly written | WP |
24.1.1 | 392 | 'equivalence' for input iterators | NAD |
24.1.2 | 324 | Do output iterators have value types? | WP |
24.1.3 | 200 | Forward iterator requirements don't allow constant iterators | WP |
24.1.3 | 476 | Forward Iterator implied mutability | New |
24.1.3 | 477 | Operator-> for const forward iterators | New |
24.1.3 | 478 | Should forward iterator requirements table have a line for r->m? | New |
24.1.4 | 299 | Incorrect return types for iterator dereference | Open |
24.1.4 | 383 | Bidirectional iterator assertion typo | WP |
24.1.5 | 299 | Incorrect return types for iterator dereference | Open |
24.1.5 | 448 | Random Access Iterators over abstract classes | Ready |
24.1.5 | 458 | 24.1.5 contains unintented limitation for operator- | Open |
24.3.1 | 445 | iterator_traits::reference unspecified for some iterator categories | Review |
24.3.2 | 257 | STL functional object and iterator inheritance. | NAD |
24.3.4 | 204 | distance(first, last) when "last" is before "first" | NAD |
24.4.1 | 280 | Comparison of reverse_iterator to const reverse_iterator | Open |
24.4.1.1 | 235 | No specification of default ctor for reverse_iterator | WP |
24.4.1.3.11 | 386 | Reverse iterator's operator[] has impossible return type | Review |
24.4.1.3.13 | 99 | Reverse_iterator comparisons completely wrong | NAD |
24.4.2 | 100 | Insert iterators/ostream_iterators overconstrained | NAD |
24.5.1 | 245 | Which operations on istream_iterator trigger input operations? | NAD |
24.5.1.2 | 260 | Inconsistent return type of istream_iterator::operator++(int) | WP |
24.5.1.2 | 261 | Missing description of istream_iterator::operator!= | WP |
24.5.2 | 349 | Minor typographical error in ostream_iterator | WP |
24.5.3 | 110 | istreambuf_iterator::equal not const | TC |
24.5.3.4 | 39 | istreambuf_iterator<>::operator++(int) definition garbled | TC |
24.5.3.5 | 110 | istreambuf_iterator::equal not const | TC |
24.5.3.5 | 111 | istreambuf_iterator::equal overspecified, inefficient | NAD Future |
24.5.4 | 100 | Insert iterators/ostream_iterators overconstrained | NAD |
24.5.4.1 | 112 | Minor typo in ostreambuf_iterator constructor | TC |
25 | 92 | Incomplete Algorithm Requirements | WP |
25 | 210 | distance first and last confused | TC |
25 | 431 | Swapping containers with unequal allocators | Open |
25.1.1 | 290 | Requirements to for_each and its function object | Open |
25.1.1 | 475 | May the function object passed to for_each modify the elements of the iterated sequence? | New |
25.1.2 | 219 | find algorithm missing version that takes a binary predicate argument | NAD Future |
25.1.2 | 244 | Must find's third argument be CopyConstructible? | NAD |
25.1.4 | 150 | Find_first_of says integer instead of iterator | TC |
25.1.5 | 240 | Complexity of adjacent_find() is meaningless | WP |
25.1.9 | 426 | search_n(), fill_n(), and generate_n() with negative n | Ready |
25.2.2 | 187 | iter_swap underspecified | WP |
25.2.2 | 227 | std::swap() should require CopyConstructible or DefaultConstructible arguments | TC |
25.2.3 | 242 | Side effects of function objects | WP |
25.2.3 | 293 | Order of execution in transform algorithm | NAD |
25.2.4 | 283 | std::replace() requirement incorrect/insufficient | WP |
25.2.4 | 337 | replace_copy_if's template parameter should be InputIterator | WP |
25.2.5 | 426 | search_n(), fill_n(), and generate_n() with negative n | Ready |
25.2.6 | 426 | search_n(), fill_n(), and generate_n() with negative n | Ready |
25.2.7 | 367 | remove_copy/remove_copy_if and Input Iterators | NAD |
25.2.8 | 202 | unique() effects unclear when predicate not an equivalence relation | WP |
25.2.8 | 239 | Complexity of unique() and/or unique_copy incorrect | WP |
25.2.8 | 241 | Does unique_copy() require CopyConstructible and Assignable? | WP |
25.2.8 | 481 | unique's effects on the range [result, last) | New |
25.2.9 | 223 | reverse algorithm should use iter_swap rather than swap | TC |
25.3 | 218 | Algorithms do not use binary predicate objects for default comparisons | NAD |
25.3.3 | 191 | Unclear complexity for algorithms such as binary search | NAD |
25.3.3 | 270 | Binary search requirements overly strict | WP |
25.3.3.3 | 384 | equal_range has unimplementable runtime complexity | Open |
25.3.3.3 | 472 | Missing "Returns" clause in std::equal_range | New |
25.3.5 | 291 | Underspecification of set algorithms | WP |
25.3.5 | 411 | Wrong names of set member functions | WP |
25.3.6 | 193 | Heap operations description incorrect | TC |
25.3.7 | 190 | min() and max() functions should be std::binary_functions | NAD Future |
25.3.7 | 212 | Empty range behavior unclear for several algorithms | TC |
25.3.7 | 281 | std::min() and max() requirements overly restrictive | WP |
25.3.8 | 142 | lexicographical_compare complexity wrong | TC |
25.4 | 286 | <cstdlib> requirements missing size_t typedef | WP |
25.4 | 405 | qsort and POD | Ready |
26.2 | 387 | std::complex over-encapsulated | Open |
26.2 | 388 | Use of complex as a key in associative containers | NAD Future |
26.2.1 | 79 | Inconsistent declaration of polar() | TC |
26.2.1 | 80 | Global Operators of complex declared twice | TC |
26.2.2 | 80 | Global Operators of complex declared twice | TC |
26.2.6 | 146 | complex<T> Inserter and Extractor need sentries | TC |
26.2.6 | 177 | Complex operators cannot be explicitly instantiated | NAD |
26.2.7 | 79 | Inconsistent declaration of polar() | TC |
26.2.8 | 440 | Should std::complex use unqualified transcendentals? | NAD |
26.3 | 93 | Incomplete Valarray Subset Definitions | NAD |
26.3.2 | 107 | Valarray constructor is strange | NAD |
26.3.2 | 125 | valarray<T>::operator!() return type is inconsistent | TC |
26.3.2 | 389 | Const overload of valarray::operator[] returns by value | WP |
26.3.2.1 | 253 | valarray helper functions are almost entirely useless | WP |
26.3.2.2 | 253 | valarray helper functions are almost entirely useless | WP |
26.3.2.3 | 77 | Valarray operator[] const returning value | NAD Future |
26.3.2.4 | 430 | valarray subset operations | Open |
26.3.2.6 | 188 | valarray helpers missing augmented assignment operators | NAD Future |
26.3.5 | 81 | Wrong declaration of slice operations | NAD |
26.3.5 | 106 | Numeric library private members are implementation defined | TC |
26.3.5.4 | 123 | Should valarray helper arrays fill functions be const? | WP |
26.3.7 | 81 | Wrong declaration of slice operations | NAD |
26.3.7.4 | 123 | Should valarray helper arrays fill functions be const? | WP |
26.3.8 | 81 | Wrong declaration of slice operations | NAD |
26.3.8.4 | 123 | Should valarray helper arrays fill functions be const? | WP |
26.3.9 | 81 | Wrong declaration of slice operations | NAD |
26.3.9.4 | 123 | Should valarray helper arrays fill functions be const? | WP |
26.4 | 242 | Side effects of function objects | WP |
26.5 | 213 | Math function overloads ambiguous | NAD |
26.5 | 289 | <cmath> requirements missing C float and long double versions | NAD |
26.5 | 295 | Is abs defined in <cmath>? | WP |
26.5 | 323 | abs() overloads in different headers | NAD Future |
26.5 | 357 | <cmath> float functions cannot return HUGE_VAL | NAD |
26.5 | 395 | inconsistencies in the definitions of rand() and random_shuffle() | WP |
27 | 44 | Iostreams use operator== on int_type values | WP |
27 | 55 | Invalid stream position is undefined | TC |
27 | 273 | Missing ios_base qualification on members of a dependent class | WP |
27 | 308 | Table 82 mentions unrelated headers | WP |
27 | 343 | Unspecified library header dependencies | NAD Future |
27 | 365 | Lack of const-qualification in clause 27 | WP |
27 | 366 | Excessive const-qualification | Open |
27 | 423 | effects of negative streamsize in iostreams | Open |
27.3 | 155 | Typo in naming the class defining the class Init | TC |
27.3 | 369 | io stream objects and static ctors | Review |
27.3 | 455 | cerr::tie() and wcerr::tie() are overspecified | Review |
27.3.1 | 29 | Ios_base::init doesn't exist | TC |
27.3.1 | 178 | Should clog and cerr initially be tied to cout? | NAD |
27.4 | 35 | No manipulator unitbuf in synopsis | TC |
27.4.2 | 41 | Ios_base needs clear(), exceptions() | TC |
27.4.2 | 50 | Copy constructor and assignment operator of ios_base | TC |
27.4.2 | 78 | Typo: event_call_back | TC |
27.4.2.1.1 | 48 | Use of non-existent exception constructor | TC |
27.4.2.1.1 | 331 | bad declaration of destructor for ios_base::failure | WP |
27.4.2.1.1 | 363 | Missing exception specification in 27.4.2.1.1 | WP |
27.4.2.1.6 | 418 | exceptions thrown during iostream cleanup | Open |
27.4.2.2 | 189 | setprecision() not specified correctly | TC |
27.4.2.2 | 287 | conflicting ios_base fmtflags | NAD |
27.4.2.3 | 47 | Imbue() and getloc() Returns clauses swapped | TC |
27.4.2.3 | 156 | Typo in imbue() description | TC |
27.4.2.4 | 49 | Underspecification of ios_base::sync_with_stdio | WP |
27.4.2.5 | 36 | Iword & pword storage lifetime omitted | TC |
27.4.2.5 | 157 | Meaningless error handling for pword() and iword() | Dup |
27.4.2.7 | 220 | ~ios_base() usage valid? | TC |
27.4.3 | 6 | File position not an offset unimplementable | NAD |
27.4.3 | 332 | Consider adding increment and decrement operators to std::fpos< T > | NAD |
27.4.3 | 441 | Is fpos::state const? | Ready |
27.4.3.2 | 52 | Small I/O problems | TC |
27.4.4 | 194 | rdbuf() functions poorly specified | NAD |
27.4.4.1 | 53 | Basic_ios destructor unspecified | TC |
27.4.4.1 | 145 | adjustfield lacks default value | NAD |
27.4.4.2 | 256 | typo in 27.4.4.2, p17: copy_event does not exist | WP |
27.4.4.2 | 292 | effects of a.copyfmt (a) | WP |
27.4.4.3 | 272 | Missing parentheses around subexpression | WP |
27.4.4.3 | 412 | Typo in 27.4.4.3 | Ready |
27.4.4.3 | 429 | typo in basic_ios::clear(iostate) | Dup |
27.4.4.3 | 468 | unexpected consequences of ios_base::operator void*() | New |
27.5.2 | 56 | Showmanyc's return type | TC |
27.5.2 | 122 | streambuf/wstreambuf description should not say they are specializations | TC |
27.5.2 | 255 | Why do basic_streambuf<>::pbump() and gbump() take an int? | NAD Future |
27.5.2.1 | 54 | Basic_streambuf's destructor | TC |
27.5.2.1 | 421 | is basic_streambuf copy-constructible? | Open |
27.5.2.3.1 | 59 | Ambiguity in specification of gbump | TC |
27.5.2.4.2 | 158 | Underspecified semantics for setbuf() | TC |
27.5.2.4.2 | 364 | Inconsistent wording in 27.5.2.4.2 | WP |
27.5.2.4.3 | 159 | Strange use of underflow() | TC |
27.5.2.4.4 | 32 | Pbackfail description inconsistent | TC |
27.6 | 309 | Does sentry catch exceptions? | Open |
27.6.1.1 | 113 | Missing/extra iostream sync semantics | NAD |
27.6.1.1 | 160 | Typo: Use of non-existing function exception() | TC |
27.6.1.1.2 | 26 | Bad sentry example | TC |
27.6.1.1.2 | 195 | Should basic_istream::sentry's constructor ever set eofbit? | TC |
27.6.1.1.2 | 203 | basic_istream::sentry::sentry() is uninstantiable with ctype<user-defined type> | NAD |
27.6.1.1.2 | 419 | istream extractors not setting failbit if eofbit is already set | Open |
27.6.1.2.1 | 60 | What is a formatted input function? | TC |
27.6.1.2.1 | 373 | Are basic_istream and basic_ostream to use (exceptions()&badbit) != 0 ? | WP |
27.6.1.2.2 | 118 | basic_istream uses nonexistent num_get member functions | WP |
27.6.1.2.2 | 161 | Typo: istream_iterator vs. istreambuf_iterator | TC |
27.6.1.2.3 | 13 | Eos refuses to die | TC |
27.6.1.2.3 | 58 | Extracting a char from a wide-oriented stream | NAD |
27.6.1.2.3 | 64 | Exception handling in basic_istream::operator>>(basic_streambuf*) | TC |
27.6.1.2.3 | 68 | Extractors for char* should store null at end | TC |
27.6.1.2.3 | 162 | Really "formatted input functions"? | Dup |
27.6.1.2.3 | 413 | Proposed resolution to LDR#64 still wrong | Review |
27.6.1.3 | 61 | Ambiguity in iostreams exception policy | TC |
27.6.1.3 | 62 | Sync's return value | TC |
27.6.1.3 | 113 | Missing/extra iostream sync semantics | NAD |
27.6.1.3 | 129 | Need error indication from seekp() and seekg() | TC |
27.6.1.3 | 136 | seekp, seekg setting wrong streams? | WP |
27.6.1.3 | 163 | Return of gcount() after a call to gcount | Dup |
27.6.1.3 | 172 | Inconsistent types for basic_istream::ignore() | TC |
27.6.1.3 | 243 | get and getline when sentry reports failure | WP |
27.6.1.3 | 342 | seek and eofbit | Open |
27.6.1.3 | 370 | Minor error in basic_istream::get | WP |
27.6.1.3 | 399 | volations of unformatted input function requirements | NAD |
27.6.1.4 | 415 | behavior of std::ws | Ready |
27.6.1.5 | 271 | basic_iostream missing typedefs | WP |
27.6.1.5.1 | 135 | basic_iostream doubly initialized | NAD |
27.6.2.1 | 165 | xsputn(), pubsync() never called by basic_ostream members? | WP |
27.6.2.1 | 311 | Incorrect wording in basic_ostream class synopsis | WP |
27.6.2.3 | 397 | ostream::sentry dtor throws exceptions | Open |
27.6.2.3 | 398 | effects of end-of-file on unformatted input functions | Open |
27.6.2.3 | 442 | sentry::operator bool() inconsistent signature | Ready |
27.6.2.4 | 129 | Need error indication from seekp() and seekg() | TC |
27.6.2.5.1 | 373 | Are basic_istream and basic_ostream to use (exceptions()&badbit) != 0 ? | WP |
27.6.2.5.1 | 394 | behavior of formatted output on failure | Open |
27.6.2.5.2 | 117 | basic_ostream uses nonexistent num_put member functions | WP |
27.6.2.5.2 | 437 | Formatted output of function pointers is confusing | NAD |
27.6.2.5.3 | 166 | Really "formatted output functions"? | Dup |
27.6.2.5.4 | 167 | Improper use of traits_type::length() | WP |
27.6.2.5.4 | 474 | confusing Footnote 297 | New |
27.6.2.6 | 63 | Exception-handling policy for unformatted output | TC |
27.6.2.6 | 168 | Typo: formatted vs. unformatted | TC |
27.6.2.7 | 333 | does endl imply synchronization with the device? | WP |
27.6.3 | 183 | I/O stream manipulators don't work for wide character streams | WP |
27.6.3 | 216 | setbase manipulator description flawed | Dup |
27.7 | 128 | Need open_mode() function for file stream, string streams, file buffers, and string buffers | NAD Future |
27.7 | 252 | missing casts/C-style casts used in iostreams | WP |
27.7.1 | 251 | basic_stringbuf missing allocator_type | WP |
27.7.1.1 | 238 | Contradictory results of stringbuf initialization. | WP |
27.7.1.3 | 169 | Bad efficiency of overflow() mandated | TC |
27.7.1.3 | 375 | basic_ios should be ios_base in 27.7.1.3 | WP |
27.7.1.3 | 376 | basic_streambuf semantics | Open |
27.7.1.3 | 432 | stringbuf::overflow() makes only one write position available | Ready |
27.7.1.3 | 453 | basic_stringbuf::seekoff need not always fail for an empty stream | Review |
27.7.3 | 45 | Stringstreams read/write pointers initial position unclear | NAD |
27.7.4 | 170 | Inconsistent definition of traits_type | TC |
27.8 | 105 | fstream ctors argument types desired | NAD Future |
27.8 | 128 | Need open_mode() function for file stream, string streams, file buffers, and string buffers | NAD Future |
27.8.1 | 73 | is_open should be const | NAD |
27.8.1 | 420 | is std::FILE a complete type? | WP |
27.8.1 | 444 | Bad use of casts in fstream | Review |
27.8.1 | 460 | Default modes missing from basic_fstream member specifications | New |
27.8.1.3 | 443 | filebuf::close() inconsistent use of EOF | Ready |
27.8.1.3 | 454 | basic_filebuf::open should accept wchar_t names | Review |
27.8.1.4 | 171 | Strange seekpos() semantics due to joint position | WP |
27.8.1.4 | 173 | Inconsistent types for basic_filebuf::setbuf() | TC |
27.8.1.6 | 285 | minor editorial errors in fstream ctors | WP |
27.8.1.7 | 22 | Member open vs. flags | TC |
27.8.1.7 | 409 | Closing an fstream should clear error state | Review |
27.8.1.10 | 409 | Closing an fstream should clear error state | Review |
D.5 | 143 | C .h header wording unclear | NAD |
D.6 | 174 | Typo: OFF_T vs. POS_T | TC |
D.6 | 175 | Ambiguity for basic_streambuf::pubseekpos() and a few other functions. | TC |
D.6 | 176 | exceptions() in ios_base...? | TC |
D.7 | 46 | Minor Annex D errors | TC |
D.7.1.3 | 65 | Underspecification of strstreambuf::seekoff | NAD |
D.7.1.3 | 66 | Strstreambuf::setbuf | TC |
D.7.1.3 | 267 | interaction of strstreambuf::overflow() and seekoff() | NAD |
D.7.4.1 | 115 | Typo in strstream constructors | TC |
----- End of document -----