When is the ANSI/ISO C++ standardization committee expected to finalize
the new C++ standard?

-----------------------------------------------------------------------------
Kevin S. Van Horn     | It is the means that determine the ends.
vanhorn@architext.com |


---
[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]

Here is the current schedule for completing the ISO standard. The
schedule assumes that all votes are affirmative. If a vote at any
stage rejects the draft standard, slip the schedule by at least
6 months from that point.

11/95 WG21 Mtg #14
 3/96 WG21 Resolve CD ballot; Mtg #15
 4/96 WG21 Complete editorial corrections.
 5/96 SC22 Final CD ballot 3 mos.
 7/96 WG21 Mtg #16.
11/96 WG21 Mtg #17
 3/97 WG21 Resolve Final CD ballot; Mtg #18
 4/97 WG21 Complete editorial corrections
 5/97 JTC1 DIS ballot 4 mos.
 7/97 WG21 Mtg #19.
12/97 WG21 Complete editorial corrections.
           ITTF receives IS from WG21 Editor for publication via SC22
           secretariat (with final report).

The ISO side of the C++ Committee is called WG21, and is under SC22,
which is under JTC1. A "CD" is the Committee Draft, which is a version
of the draft standard submitted for approval. When the CD is approved,
it becomes a Draft International Standard ("DIS"). With final approval,
it becomes an International Standard ("IS") and is published.

>From the point of the CD ballot no substantive changes are permitted
without causing another CD round and slipped schedule. Typographical
erros may be corrected, but not much else. So the final standard should
be nearly identical to the CD of 5/96, assuming all votes are affirmative.
---
Steve Clamage, stephen.clamage@eng.sun.com
acting chair, ANSI C++ Committee X3J16



---
[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]