You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stdcxx.apache.org by se...@apache.org on 2008/08/16 20:48:32 UTC
svn commit: r686536 - /stdcxx/site/status/2008-08.text
Author: sebor
Date: Sat Aug 16 11:48:31 2008
New Revision: 686536
URL: http://svn.apache.org/viewvc?rev=686536&view=rev
Log:
2008-08-16 Martin Sebor <se...@apache.org>
* status/2008-08.text: Fixed typos.
Modified:
stdcxx/site/status/2008-08.text
Modified: stdcxx/site/status/2008-08.text
URL: http://svn.apache.org/viewvc/stdcxx/site/status/2008-08.text?rev=686536&r1=686535&r2=686536&view=diff
==============================================================================
--- stdcxx/site/status/2008-08.text (original)
+++ stdcxx/site/status/2008-08.text Sat Aug 16 11:48:31 2008
@@ -1,13 +1,13 @@
Notable changes since the last report (May 2008):
- The reelase schedule for the next C++ standard, informally known as
- C++ 0x, has changed. The new standard is now expected to be
- reatified sometime in 2011 rather than by the end of this decade as
- originally planned. The team's progress on the implementation of the
- new C++ standard features has been slow in part due to ongoing
- changes to the specification and in part due to the limited
- availability of the new core C++ features in existing compilers, or
- their instability.
+ The release schedule for the next C++ standard, informally known
+ as C++ 0x, has changed. The new standard is now expected to be
+ ratified sometime in 2011 rather than by the end of this decade
+ as originally planned. The team's progress on the implementation
+ of the new C++ standard features has been slow in part due to
+ ongoing changes to the specification and in part due to the limited
+ availability of the new core C++ features in existing compilers,
+ or their instability.
BIS Export Control Classification: