|Document number:||N1639 = 04-0079|
|Date:||April 12, 2004|
|Project:||Programming Language C++|
|Reference:||ISO/IEC IS 14882:2003(E)|
|Reply to:||Pete Becker|
· Editorial Changes
N1638=04-0079, Working Draft, Standard for Programming Language C++, contains the body of the standard, with all of the changes made at the Sydney meeting. It has diff marks reflecting these changes. Note that the diff marks are generated from the troff source files, and the results go through some further processing before being typeset; one consequence is that diff marks sometimes appear a line or two away from the actual difference, and sometimes persist for several lines, especially in tables and footnotes. The marks should be taken as a guide to where changes occurred, and not as literal truth.
Partway through Clause 24, Iterators, there's a very long series of diff marks, extending into Clause 25. This is a diff artifact, and should not be taken seriously.
There were a few places where the changes described in the defect reports did not accurately reflect the intent of the report. When the intent was clear and the correct wording was obvious, I made the correction. I also made some editorial changes.
My thanks to Barry Hedquist, John Spicer, and Steve Adamczyk for their proofreading. If we're lucky, our jetlag-induced errors didn't overlap.
to_int_type, so the text reads
traits::eq_int_type(traits::to_int_type(c), delim)instead of the proposed
[lib.istream::sentry]/6; that paragraph was removed in TC1, so I didn't change it.
at(xpos+I) == str.at(I)to
traits::eq(at(xpos+I), str.at(I))but the actual code is
at(xpos) == str.at(I)which is correct, so the change I made is:
Requiresclauses to better match the style used in other parts of the WP.
T operator(size_t const);to
const T& operator(size_t const);This is obviously a typo, and the
constafter the argument should be after the closing parenthesis.
Yes, there will be Bookmarks and a Table of Contents. Between now and the
next meeting I'll be converting the base text from troff to LaTeX, which will
improve maintainability, simplify builds, and provide more flexibility. That's
obviously an exacting job. Adobe® Acrobat® can
compare the text in two