Francis Glassborow wrote in message ...
>However it is all very academic because the chance that WG21 working
>with J16 would get anywhere near a new release in the next four years is
>infinitesimal.  We have too much work cleaning up the present release.

    Well, I'm not sure that's entirely true.  As I remember from the last
meeting, one of the primary concerns when reviewing an issue was if it was a
correction for the Defect Report, or an addition which had to wait for the
Next Standard.  Enough fell into the latter category that I think the
committee could have a reasonable sized Amendment 1 ready by 2003.

--
Truth,
   James
http://www.NJTheater.Com       -and-
http://www.NJTheater.Com/JamesCurran
---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html              ]

In article <043935902160289CPIMSSMTPU07@email.msn.com>, James Curran
<JamesCurran@msn.com> writes
>    Well, I'm not sure that's entirely true.  As I remember from the last
>meeting, one of the primary concerns when reviewing an issue was if it was a
>correction for the Defect Report, or an addition which had to wait for the
>Next Standard.  Enough fell into the latter category that I think the
>committee could have a reasonable sized Amendment 1 ready by 2003.

we are not talking about the same thing.  A corrigendum is not a new
standard but a correction to an existing one.  The former we should
certainly deliver in a timely fashion.

Francis Glassborow      Journal Editor, Association of C & C++ Users
64 Southfield Rd
Oxford OX4 1PA          +44(0)1865 246490
All opinions are mine and do not represent those of any organisation


[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html              ]

Francis Glassborow <francis@robinton.demon.co.uk> writes:

>In article <043935902160289CPIMSSMTPU07@email.msn.com>, James Curran
><JamesCurran@msn.com> writes
>>    Well, I'm not sure that's entirely true.  As I remember from the last
>>meeting, one of the primary concerns when reviewing an issue was if it was a
>>correction for the Defect Report, or an addition which had to wait for the
>>Next Standard.  Enough fell into the latter category that I think the
>>committee could have a reasonable sized Amendment 1 ready by 2003.

>we are not talking about the same thing.  A corrigendum is not a new
>standard but a correction to an existing one.  The former we should
>certainly deliver in a timely fashion.

Well, now we're talking about 3 different things. :-)

1. A Technical Corrigendum corrects defects (errors, omissions,
ambiguities) in the standard. The C++ committee has already decided
to issue one or two TCs in response to reported defects. A TC
cannot add substantial new features.

2. An Amendment can add new features.

3. A new standard can be issued.

In principle, the C++ committee could produce an Amendment
adding new features before working on a revision of the standard.
I'm unaware of any significant support within the committee for
such a move, however.

--
Steve Clamage, stephen.clamage@sun.com
---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html              ]

In article <0bd795238151b79CPIMSSMTPU07@email.msn.com>, James Curran
<JamesCurran@msn.com> writes
>    Could someone clarify something about the C++ Standard.  I've been told
>that by ISO rules the current standard cannot change for 5 years.  But what
>exactly does that mean?
>
>    o The committee cannot begin work on the next standard for 5 years.

No.
>    o The committee cannot vote out a new FDIS for 5 years.  -or --
I think yes
>    o ISO cannot approve another FDIS for 5 years (the FDIS presumably being
>voted out a few months earlier) ???
I think yes

However it is all very academic because the chance that WG21 working
with J16 would get anywhere near a new release in the next four years is
infinitesimal.  We have too much work cleaning up the present release.
You should not expect a new version for at least ten years.  In addition
I believe that SC22 has to authorise a work item and they are unlikely
to do that for quite a few years (like about four)



Francis Glassborow      Journal Editor, Association of C & C++ Users
64 Southfield Rd
Oxford OX4 1PA          +44(0)1865 246490
All opinions are mine and do not represent those of any organisation
---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html              ]

    Could someone clarify something about the C++ Standard.  I've been told
that by ISO rules the current standard cannot change for 5 years.  But what
exactly does that mean?

    o The committee cannot begin work on the next standard for 5 years.
    o The committee cannot vote out a new FDIS for 5 years.  -or --
    o ISO cannot approve another FDIS for 5 years (the FDIS presumably being
voted out a few months earlier) ???

--
Truth,
   James
http://www.NJTheater.Com       -and-
http://www.NJTheater.Com/JamesCurran
---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html              ]

In article <0bd795238151b79CPIMSSMTPU07@email.msn.com> "James Curran" <JamesCurran@msn.com> writes:
>    Could someone clarify something about the C++ Standard.  I've been told
>that by ISO rules the current standard cannot change for 5 years.  But what
>exactly does that mean?
>
>    o The committee cannot begin work on the next standard for 5 years.
>    o The committee cannot vote out a new FDIS for 5 years.  -or --
>    o ISO cannot approve another FDIS for 5 years (the FDIS presumably being
>voted out a few months earlier) ???

It's my understanding that in no more than 5 years (that's the max time
I believe, it could be less) the Standard is _reviewed_ for _subsequent_
"revision" considerations.

I don't think this is important per se though.  What's important
is that the committee has some current "projects" (Defect Reports,
and the Performance Technical Report) and in that process is not
discarding potential revision considerations that come up.

In the meantime, on going current practice et al offers the community
the opportunity to assess state of the art and such as it occurs.
Mind you, the review is not just to detect issues at a micro level,
but to review the Standard as a whole too.

- Greg
--
       Comeau Computing, 91-34 120th Street, Richmond Hill, NY, 11418-3214
     Producers of Comeau C/C++ 4.2.38 -- New Release!  We now do Windows too.
    Email: comeau@comeaucomputing.com / Voice:718-945-0009 / Fax:718-441-2310
                *** WEB: http://www.comeaucomputing.com ***


[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html              ]