Return-Path: Delivered-To: apmail-stdcxx-commits-archive@www.apache.org Received: (qmail 18321 invoked from network); 4 Feb 2008 21:21:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Feb 2008 21:21:29 -0000 Received: (qmail 94609 invoked by uid 500); 4 Feb 2008 21:21:21 -0000 Delivered-To: apmail-stdcxx-commits-archive@stdcxx.apache.org Received: (qmail 94593 invoked by uid 500); 4 Feb 2008 21:21:21 -0000 Mailing-List: contact commits-help@stdcxx.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@stdcxx.apache.org Delivered-To: mailing list commits@stdcxx.apache.org Received: (qmail 94583 invoked by uid 99); 4 Feb 2008 21:21:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Feb 2008 13:21:21 -0800 X-ASF-Spam-Status: No, hits=-99.1 required=10.0 tests=ALL_TRUSTED,NORMAL_HTTP_TO_IP,URIBL_RHS_DOB X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO eris.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Feb 2008 21:20:59 +0000 Received: by eris.apache.org (Postfix, from userid 65534) id E4B6D1A9832; Mon, 4 Feb 2008 13:20:46 -0800 (PST) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r618441 [1/3] - in /stdcxx/site/forrest: ./ src/ src/documentation/ src/documentation/classes/ src/documentation/content/ src/documentation/content/xdocs/ src/documentation/content/xdocs/images/ src/documentation/resources/ src/documentatio... Date: Mon, 04 Feb 2008 21:20:41 -0000 To: commits@stdcxx.apache.org From: sebor@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20080204212047.E4B6D1A9832@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: sebor Date: Mon Feb 4 13:20:33 2008 New Revision: 618441 URL: http://svn.apache.org/viewvc?rev=618441&view=rev Log: 2008-02-04 Gavin STDCXX-686 * forrest/forrest.properties: Added sources for the initial (though incomplete) pass at a Forrest-based site redesign/reimplementation. * forrest/src/documentation: Same. * forrest/src/documentation/sitemap.xmap: Same. * forrest/src/documentation/skinconf.xml: Same. * forrest/src/documentation/content: Same. * forrest/src/documentation/content/xdocs: Same. * forrest/src/documentation/content/xdocs/bugs.xml: Same. * forrest/src/documentation/content/xdocs/site.xml: Same. * forrest/src/documentation/content/xdocs/images: Same. * forrest/src/documentation/content/xdocs/images/project.svg: Same. * forrest/src/documentation/content/xdocs/images/project-logo.gif: Same. * forrest/src/documentation/content/xdocs/images/group.svg: Same. * forrest/src/documentation/content/xdocs/images/icon.png: Same. * forrest/src/documentation/content/xdocs/images/group-logo.gif: Same. * forrest/src/documentation/content/xdocs/images/usemap.gif: Same. * forrest/src/documentation/content/xdocs/download.xml: Same. * forrest/src/documentation/content/xdocs/index.xml: Same. * forrest/src/documentation/content/xdocs/tabs.xml: Same. * forrest/src/documentation/content/locationmap.xml: Same. * forrest/src/documentation/resources: Same. * forrest/src/documentation/resources/schema: Same. * forrest/src/documentation/resources/schema/catalog.xcat: Same. * forrest/src/documentation/resources/themes: Same. * forrest/src/documentation/resources/themes/pelt: Same. * forrest/src/documentation/resources/themes/pelt/panels: Same. * forrest/src/documentation/resources/themes/pelt/panels/pelt-html.panel.xml: Same. * forrest/src/documentation/resources/themes/pelt/panels/pelt-css.panel.xml: Same. * forrest/src/documentation/resources/themes/pelt/html: Same. * forrest/src/documentation/resources/themes/pelt/html/siteinfo-credits.ft: Same. * forrest/src/documentation/resources/themes/pelt/html/content-main.ft: Same. * forrest/src/documentation/resources/themes/pelt/html/nav-main-sub.ft: Same. * forrest/src/documentation/resources/themes/pelt/html/nav-section-round-bottom.ft: Same. * forrest/src/documentation/resources/themes/pelt/html/search-input.ft: Same. * forrest/src/documentation/resources/themes/pelt/html/branding-logo.ft: Same. * forrest/src/documentation/resources/themes/pelt/images: Same. * forrest/src/documentation/resources/themes/pelt/images/page.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/spacer.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/singlepage.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/label.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/search-right.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/sidebar_bg.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/tab-right.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/current.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/printer.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/header-background.png: Same. * forrest/src/documentation/resources/themes/pelt/images/chapter.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/xmldoc.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/chapter_white.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/tl-off.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/tl-on.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/tr-off.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/search-left.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/tab-left.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/header-background-grad.png: Same. * forrest/src/documentation/resources/themes/pelt/images/header_white_line.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/pdfdoc.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/tr-on.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/header-background.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/doc.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/chapter_open.gif: Same. * forrest/src/documentation/resources/themes/pelt/images/instruction_arrow.png: Same. * forrest/src/documentation/resources/themes/pelt/css: Same. * forrest/src/documentation/resources/themes/pelt/css/pelt.print.css: Same. * forrest/src/documentation/resources/themes/pelt/css/leather-dev.css: Same. * forrest/src/documentation/resources/themes/pelt/css/pelt.screen.css: Same. * forrest/src/documentation/resources/themes/pelt/css/pelt.basic.css: Same. * forrest/src/documentation/resources/themes/common: Same. * forrest/src/documentation/resources/themes/common/css: Same. * forrest/src/documentation/resources/themes/common/css/branding-theme-profiler.ft: Same. * forrest/src/documentation/resources/themes/pelt.fv: Same. * forrest/src/documentation/resources/images: Same. * forrest/src/documentation/resources/images/stdcxx.png: Same. * forrest/src/documentation/resources/images/Thumbs.db: Same. * forrest/src/documentation/README.txt: Same. * forrest/src/documentation/classes: Same. * forrest/src/documentation/classes/CatalogManager.properties: Same. * forrest/forrest.properties.xml: Same. Added: stdcxx/site/forrest/ stdcxx/site/forrest/forrest.properties (with props) stdcxx/site/forrest/forrest.properties.xml (with props) stdcxx/site/forrest/src/ stdcxx/site/forrest/src/documentation/ stdcxx/site/forrest/src/documentation/README.txt (with props) stdcxx/site/forrest/src/documentation/classes/ stdcxx/site/forrest/src/documentation/classes/CatalogManager.properties (with props) stdcxx/site/forrest/src/documentation/content/ stdcxx/site/forrest/src/documentation/content/locationmap.xml (with props) stdcxx/site/forrest/src/documentation/content/xdocs/ stdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml (with props) stdcxx/site/forrest/src/documentation/content/xdocs/download.xml (with props) stdcxx/site/forrest/src/documentation/content/xdocs/images/ stdcxx/site/forrest/src/documentation/content/xdocs/images/group-logo.gif (with props) stdcxx/site/forrest/src/documentation/content/xdocs/images/group.svg (with props) stdcxx/site/forrest/src/documentation/content/xdocs/images/icon.png (with props) stdcxx/site/forrest/src/documentation/content/xdocs/images/project-logo.gif (with props) stdcxx/site/forrest/src/documentation/content/xdocs/images/project.svg (with props) stdcxx/site/forrest/src/documentation/content/xdocs/images/usemap.gif (with props) stdcxx/site/forrest/src/documentation/content/xdocs/index.xml (with props) stdcxx/site/forrest/src/documentation/content/xdocs/site.xml (with props) stdcxx/site/forrest/src/documentation/content/xdocs/tabs.xml (with props) stdcxx/site/forrest/src/documentation/resources/ stdcxx/site/forrest/src/documentation/resources/images/ stdcxx/site/forrest/src/documentation/resources/images/Thumbs.db (with props) stdcxx/site/forrest/src/documentation/resources/images/stdcxx.png (with props) stdcxx/site/forrest/src/documentation/resources/schema/ stdcxx/site/forrest/src/documentation/resources/schema/catalog.xcat (with props) stdcxx/site/forrest/src/documentation/resources/themes/ stdcxx/site/forrest/src/documentation/resources/themes/common/ stdcxx/site/forrest/src/documentation/resources/themes/common/css/ stdcxx/site/forrest/src/documentation/resources/themes/common/css/branding-theme-profiler.ft (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/ stdcxx/site/forrest/src/documentation/resources/themes/pelt.fv (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/css/ stdcxx/site/forrest/src/documentation/resources/themes/pelt/css/leather-dev.css (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/css/pelt.basic.css (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/css/pelt.print.css (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/css/pelt.screen.css (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/html/ stdcxx/site/forrest/src/documentation/resources/themes/pelt/html/branding-logo.ft (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/html/content-main.ft (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/html/nav-main-sub.ft (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/html/nav-section-round-bottom.ft (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/html/search-input.ft (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/html/siteinfo-credits.ft (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/ stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/chapter.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/chapter_open.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/chapter_white.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/current.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/doc.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/header-background-grad.png (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/header-background.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/header-background.png (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/header_white_line.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/instruction_arrow.png (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/label.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/page.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/pdfdoc.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/printer.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/search-left.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/search-right.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/sidebar_bg.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/singlepage.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/spacer.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/tab-left.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/tab-right.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/tl-off.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/tl-on.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/tr-off.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/tr-on.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/images/xmldoc.gif (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/panels/ stdcxx/site/forrest/src/documentation/resources/themes/pelt/panels/pelt-css.panel.xml (with props) stdcxx/site/forrest/src/documentation/resources/themes/pelt/panels/pelt-html.panel.xml (with props) stdcxx/site/forrest/src/documentation/sitemap.xmap (with props) stdcxx/site/forrest/src/documentation/skinconf.xml (with props) Added: stdcxx/site/forrest/forrest.properties URL: http://svn.apache.org/viewvc/stdcxx/site/forrest/forrest.properties?rev=618441&view=auto ============================================================================== --- stdcxx/site/forrest/forrest.properties (added) +++ stdcxx/site/forrest/forrest.properties Mon Feb 4 13:20:33 2008 @@ -0,0 +1,25 @@ +# Licensed to the Apache Software Foundation (ASF) under one or more +# contributor license agreements. See the NOTICE file distributed with +# this work for additional information regarding copyright ownership. +# The ASF licenses this file to You under the Apache License, Version 2.0 +# (the "License"); you may not use this file except in compliance with +# the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. + +############## +# This is a minimal properties file. +# These are defaults, un-comment them only if you need to change them. +# See the full set of default properties in a 'forrest seed-sample' site. +# Copy properties from there as needed. +############## +project.required.plugins=org.apache.forrest.plugin.output.pdf,org.apache.forrest.plugin.internal.dispatcher,org.apache.forrest.themes.core,org.apache.forrest.plugin.output.inputModule +# codename: Dispatcher +# Add the following plugins to project.required.plugins: +#org.apache.forrest.plugin.internal.dispatcher,org.apache.forrest.themes.core,org.apache.forrest.plugin.output.inputModule Propchange: stdcxx/site/forrest/forrest.properties ------------------------------------------------------------------------------ svn:eol-style = native Propchange: stdcxx/site/forrest/forrest.properties ------------------------------------------------------------------------------ svn:keywords = Id Added: stdcxx/site/forrest/forrest.properties.xml URL: http://svn.apache.org/viewvc/stdcxx/site/forrest/forrest.properties.xml?rev=618441&view=auto ============================================================================== --- stdcxx/site/forrest/forrest.properties.xml (added) +++ stdcxx/site/forrest/forrest.properties.xml Mon Feb 4 13:20:33 2008 @@ -0,0 +1,26 @@ + + + + + + + Propchange: stdcxx/site/forrest/forrest.properties.xml ------------------------------------------------------------------------------ svn:eol-style = native Propchange: stdcxx/site/forrest/forrest.properties.xml ------------------------------------------------------------------------------ svn:keywords = Id Added: stdcxx/site/forrest/src/documentation/README.txt URL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/README.txt?rev=618441&view=auto ============================================================================== --- stdcxx/site/forrest/src/documentation/README.txt (added) +++ stdcxx/site/forrest/src/documentation/README.txt Mon Feb 4 13:20:33 2008 @@ -0,0 +1,7 @@ +This is the base documentation directory. + +skinconf.xml # This file customizes Forrest for your project. In it, you + # tell forrest the project name, logo, copyright info, etc + +sitemap.xmap # Optional. This sitemap is consulted before all core sitemaps. + # See http://forrest.apache.org/docs/project-sitemap.html Propchange: stdcxx/site/forrest/src/documentation/README.txt ------------------------------------------------------------------------------ svn:eol-style = native Propchange: stdcxx/site/forrest/src/documentation/README.txt ------------------------------------------------------------------------------ svn:keywords = Id Added: stdcxx/site/forrest/src/documentation/classes/CatalogManager.properties URL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/classes/CatalogManager.properties?rev=618441&view=auto ============================================================================== --- stdcxx/site/forrest/src/documentation/classes/CatalogManager.properties (added) +++ stdcxx/site/forrest/src/documentation/classes/CatalogManager.properties Mon Feb 4 13:20:33 2008 @@ -0,0 +1,62 @@ +# Licensed to the Apache Software Foundation (ASF) under one or more +# contributor license agreements. See the NOTICE file distributed with +# this work for additional information regarding copyright ownership. +# The ASF licenses this file to You under the Apache License, Version 2.0 +# (the "License"); you may not use this file except in compliance with +# the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. + +#======================================================================= +# CatalogManager.properties for Catalog Entity Resolver. +# +# This is the default properties file for your project. +# This facilitates local configuration of application-specific catalogs. +# If you have defined any local catalogs, then they will be loaded +# before Forrest's core catalogs. +# +# See the Apache Forrest documentation: +# http://forrest.apache.org/docs/your-project.html +# http://forrest.apache.org/docs/validation.html + +# verbosity: +# The level of messages for status/debug (messages go to standard output). +# The setting here is for your own local catalogs. +# The verbosity of Forrest's core catalogs is controlled via +# main/webapp/WEB-INF/cocoon.xconf +# +# The following messages are provided ... +# 0 = none +# 1 = ? (... not sure yet) +# 2 = 1+, Loading catalog, Resolved public, Resolved system +# 3 = 2+, Catalog does not exist, resolvePublic, resolveSystem +# 10 = 3+, List all catalog entries when loading a catalog +# (Cocoon also logs the "Resolved public" messages.) +verbosity=1 + +# catalogs ... list of additional catalogs to load +# (Note that Apache Forrest will automatically load its own default catalog +# from main/webapp/resources/schema/catalog.xcat) +# Use either full pathnames or relative pathnames. +# pathname separator is always semi-colon (;) regardless of operating system +# directory separator is always slash (/) regardless of operating system +# The project catalog is expected to be at ../resources/schema/catalog.xcat +#catalogs=../resources/schema/catalog.xcat +# FIXME: Workaround FOR-548 "project DTD catalogs are not included +# when running as a servlet WAR". +# Same catalog, different path +catalogs=../resources/schema/catalog.xcat;../../project/src/documentation/resources/schema/catalog.xcat + +# relative-catalogs +# If false, relative catalog URIs are made absolute with respect to the +# base URI of the CatalogManager.properties file. This setting only +# applies to catalog URIs obtained from the catalogs property in the +# CatalogManager.properties file +# Example: relative-catalogs=[yes|no] +relative-catalogs=no Propchange: stdcxx/site/forrest/src/documentation/classes/CatalogManager.properties ------------------------------------------------------------------------------ svn:eol-style = native Propchange: stdcxx/site/forrest/src/documentation/classes/CatalogManager.properties ------------------------------------------------------------------------------ svn:keywords = Id Added: stdcxx/site/forrest/src/documentation/content/locationmap.xml URL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/locationmap.xml?rev=618441&view=auto ============================================================================== --- stdcxx/site/forrest/src/documentation/content/locationmap.xml (added) +++ stdcxx/site/forrest/src/documentation/content/locationmap.xml Mon Feb 4 13:20:33 2008 @@ -0,0 +1,47 @@ + + + + + + + + + + + + + + + + + + Propchange: stdcxx/site/forrest/src/documentation/content/locationmap.xml ------------------------------------------------------------------------------ svn:eol-style = native Propchange: stdcxx/site/forrest/src/documentation/content/locationmap.xml ------------------------------------------------------------------------------ svn:keywords = Id Added: stdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml URL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml?rev=618441&view=auto ============================================================================== --- stdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml (added) +++ stdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml Mon Feb 4 13:20:33 2008 @@ -0,0 +1,109 @@ + + + + +
+ Bugs in Apache C++ Standard Library +
+ +
+ What Is a Bug + + +

Wikipedia, the free online encyclopedia, defines a bug as follows:

+A computer bug is an error, flaw, mistake, failure, or fault in a computer program that prevents it from working correctly or produces an incorrect result. +

+
+ +
+ Before Reporting a Bug +
    +
  1. If you have discovered a bug in stdcxx and would like to report it to the development team, please be sure to first check the project's issue tracking database to see whether the bug has already been reported and, if so, what its status is. If the bug has not been reported yet, follow the instructions on Reporting a Bug below. Otherwise, feel free to add a comment to the issue in the issue tracking database if you think it might help resolve it more quickly (for example, if you have a smaller or better test case).
    2. +
  2. If you think but aren't 100% sure that you have discovered a bug in the source code of the project, please consult a reliable reference on the subject first and confirm that the behavior you are experiencing is, in fact, a bug and not a feature. If even after reading the relevant references you are still not sure, you should send an email to stdcxx-user@incubator.apache.org and ask. If the problem is indeed a bug, go back to step 1.
    3. +
  3. If you have a suggestion for a change or an addition to the interface or the behavior of this implementation of the library that you would like to propose to the development team (e.g., an enhancement request), please make sure that the change is not in conflict with the requirements of the C++ Standard. You can get an electronic copy of the C++ Standard from the ANSI eStandards store. If your request is not in conflict with any requirements of the C++ standard, open a request for Improvement or New Feature to the issue tracking database (see the stdcxx issue tracking database documentation for the available issue types).
    4. +
+
+ +
+ Saved Bug Reports +

The table below contains links to a number of saved bug tracking database queries along with their summary results. The version column indicates the version and contains a link to a query that pulls up all issues of any type scheduled to be fixed in that version. The Resolved column indicates the number of issues of any type resolved (but not closed) in that version. The Closed column indicates the number of issues of any type closed in that version. The Bugs column indicates the number of issues of type Bug resolved or closed in that version. The Improvements column indicates the number of issues of type Improvement resolved or closed in that version. The New Features column indicates the number of issues of type New Feature resolved or closed in that version. The Regressions column indicates the number of issues of any type both introduced and resolved or closed in that version. The Pending column indicates the number of issues of any type schedule for that version that haven't yet been resolved or closed.

+

The value in each cell in the table is either a number (for released versions), or TBD (for To Be Determined) for a version that is in active development, or N/A (for Not Available) for a future version for which there is no data yet.

+
+ +
+ External Bugs Affecting the Apache C++ Standard Library +

We track bugs in compilers, operating systems, and other software external to the Apache C++ Standard Library that affect the correct behavior or performance of the library or programs that use it in the issue tracking database along with other bugs. These bug reports are often quite useful when porting the project to new versions of the software. See the table below for filters with predefined searches for bugs relevant to specific compilers, operating systems, and/or common hardware architectures.

+
+ +
+ Reporting a Bug +

To report a new bug in this implementation of the C++ Standard Library or the accompanying utilities or example programs, or a problem in any other part of the stdcxx project such as its documentation or Web pages, open an issue in the project's issue tracking database and choose Bug for the Issue Type. Make sure you assign the bug the appropriate component. For example, if the bug has to do with the formatting of numbers using iostreams, the likely components will be 22. Localization, or 27. Input/Output.

+

When reporting a bug in this implementation of the library, be sure to demonstrate the problem in a small (50 lines of code or less) C++ program that does not depend on any third party libraries (system libraries excluded). In addition to the program, make sure to include the details of the environment in which the bug can be reproduces, including the full command line used to compile, link, and run the program, and the output of each of the mentioned stages, specifically any compiler or linker diagnostics, and, if applicable, the output of the program itself. When the problem manisfests itself in the form of an abnormal program termination (e.g., crash), it helps to include the full stack trace at the crash site. To demonstrate incorrect behavior, use the assert() macro to assert any postconditions. Refer to existing bug reports (such as STDCXX-2) for examples. By following this advice you will increase the chances that the bug will be resolved quickly.

+
+ +
+ Requesting an Enhancement +

The process for requesting enhancements and new features in stdcxx is essentially the same as the process for Reporting a bug except that instead choosing Bug as the Issue Type you will choose either Improvevement when requesting an enhancement to an existing feature, or New Feature when requesting an entire new feature.

+
+ +
+ Submitting Patches +

Committers who follow the Review-Then-Commit policy, and non-committer Contributors without commit (write) access to the stdcxx source repository must submit patches for review and approval before they can be committed by someone with commit access. If you would like to submit a patch for a bug that you or someone else reported, you can do so in two ways:

+
    +
  1. Post the patch to the project development mailing list, stdcxx-dev@incubator.apache.org. The subject line of the email should start with the string [PATCH], followed by a brief description of the patch and the issue number from the issue tracking database if one exists. An easy way to come up with a good description for the patch subject line is to simply copy the Summary from the bug report. Be sure to also include a reference to the bug (preferably in the form of a link to the original bug report).
    2. +
  2. Add the patch to the bug report in the form of a comment (when the patch is just a few lines of text), or in the form of an attachment to the issue. This approach is preferable to sending the patch to the mailing list when the patch is large or when the patch sent to the project development mailing list gets mangled or stripped by the list management software.
    3. +
+

If you would like to submit a patch for a bug that doesn't have a corresponding issue in the issue tracking database, you should start by creating a small test case to demonstrate the problem first. It's not uncommon for this exercise to expose an error in the usage of the library rather than in the library implementation itself. Once you've isolated the bug to a small test case and filed an issue in the issue tracking database you can update the issue with the proposed patch.

+

If you would like to submit a patch with an improvement to the project (such as an optimization tweak), either create an enhancement request in the issue tracking database and attach the patch to it or, for small changes, post the patch along with a detailed description as well as before and after data showing the improvement to the project development mailing list, stdcxx-dev@incubator.apache.org.

+

Patches for documentation or project web pages should follow the same process as above, except that a test case isn't necessary in most situations. A possible exception is a patch for code example listed in the Class Reference.

+

In all cases, make sure your patch follows the expected Patch Format described below.

+
+ +
+ Patch Format +

Every patch should address at most one issue from the issue tracking database. Separate issues should be addressed in separate patches. An issue that discusses more than one bug or one enhancement should either be first split up into multiple issues, or into multiple subtasks, before submitting a patch for each.

+

In order to make them easy to review and revert, if necessary (in case they cause regressions not dicovered during review), patches should be as small as possible. Changes should be limited to the bare minimum necessary to address the issue. Gratuitous edits such code reformatting or renanaming of variables should be avoided. Such changes should be made separately and independently of any functional changes to the code.

+

Every patch should include the following information:

+
    +
  1. Detailed description of the change. It should be obvious from reading the description alone (i.e., without reading the Change Log or looking at the source code) what the change does and why. See this post for an example of such a description.
    2. +
  2. Changes that might have an impact on the efficiency of the changed component should be accompanied by a small program exercising the component, either by timings showing the performance difference between the original and the changed code in user and system times (for example, using the POSIX time command), or by sizes of the original and the code for changes affetcting the space efficiency of code.
    3. + +
  3. Change Log entry. The format of Change Log entries follows the established GNU Change Log convention. Emacs users can take advantage of the add-change-log-entry command. See the Change Log section of the Emacs manual. + +Each Change Log entry starts with a submission date followed by the name and email address of the submitter, all on the same line. Separated by a blank line is a reference to the issue key representing the corresponding issue in the issue tracking database (if applicable). The rest of the entry consists of a bullet list of changed files and the names and descriptions of the symbols affected by the change in each file. A maximum line length of 78 characters should be observed. For examples of stdcxx Change Log entries view the logs of some stdcxx source files, such as time_put.cpp, or wcodecvt.cpp. + +The format of the issue key is especially important in order for the the issue tracking database to be able to update the issue in the issue tracking database with information about the change. The issue key format is STDCXX-NNN where the NNN part is the issue number (for example, STDCXX-2). +
    4. +
  4. The diff between the most recent versions of the file being modified and the modified version. The diff should be in a format suitable for processing by the standard POSIX patch utility, or in the Unified format produced by the Subversion svn diff command by default as well as by the GNU diff utility and understood by GNU patch. When creating patches on Windows it is important to keep in mind that the newline sequences (carriage-return followed by line-feed, or <CR><LF>) may not be recognized by traditional UNIX implementations of the patch utility (as is the case on Solaris). For portability, it is best to strip the carriage-returns from the patch before posting it. The standard tr utility can be used to do that. + +New Files +
    5. +
+
+ +
+ New Files + +

New files included as part of a patch (such as new tests) should be submitted in the original format and not as the output of the patch utility since patch cannot create new files. Multiple files can be submitted individually or as a gzipped tarball. Be aware of the size limit imposed on posts to the mailing list. In general, it is better to avoid posting very large files and instead attach them to an issue in the issue tracking database.

+

+Each new source or header file should contain the license header described in the ASF Source Header and Copyright Notice Policy. +

+
+ + + Propchange: stdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml ------------------------------------------------------------------------------ svn:eol-style = native Propchange: stdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml ------------------------------------------------------------------------------ svn:keywords = Id Added: stdcxx/site/forrest/src/documentation/content/xdocs/download.xml URL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/xdocs/download.xml?rev=618441&view=auto ============================================================================== --- stdcxx/site/forrest/src/documentation/content/xdocs/download.xml (added) +++ stdcxx/site/forrest/src/documentation/content/xdocs/download.xml Mon Feb 4 13:20:33 2008 @@ -0,0 +1,58 @@ + + + + +
+ Downloading the Apache C++ Standard Library +
+ +
+ Viewing the Latest Files Online +

The latest versions of stdcxx source files can be viewed or individually downloaded by directly accessing the stdcxx file repository in ASF Subversion by pointing your Web browser to the following URLs:

+
    +
  • trunk (development branch) http://svn.apache.org/repos/asf/stdcxx/trunk
    • +
  • 4.2.x (4.2 maintenance branch) http://svn.apache.org/repos/asf/stdcxx/branches/4.2.x
    • +
  • 4.2.0 (pre-release branch) http://svn.apache.org/repos/asf/stdcxx/branches/4.2.0 (closed to development)
    • +
  • 4.1.3 (final release branch) http://svn.apache.org/repos/asf/stdcxx/branches/4.1.3 (closed to development)
    • +
  • web site http://svn.apache.org/repos/asf/stdcxx/site
    • +
+ +
+
+ Checking Out Files Using the Subversion Client + +

+ + To check out stdcxx files using anonymous Subversion access, read the instructions here.

+To check out the latest development version of entire stdcxx repository (i.e., its trunk) into the stdcxx/ directory in current working directory, enter the following command at the command prompt:

+$ svn co http://svn.apache.org/repos/asf/stdcxx/trunk stdcxx

+To check out stdcxx files for write access (committers only), read the instructions here.

+The Subversion command is the same as above, the only thing different is the HTTPS protocol instead of ordinary HTTP:

+$ svn co https://svn.apache.org/repos/asf/stdcxx/trunk stdcxx

+

+
+
+ Downloading stdcxx Snapshots +

See the table below for available snapshots. In the table, the version column indicates the library version. The date column indicates the date the version was released. The file column contains one or more links to the tarball or zip file available for download. The size column is the size of the file in kilobytes. The md5 sum column indicates the MD5 sum for the file and is also a link pointing to the MD5 sum file that can be downloaded. The comment column contains links to the community vote approving the release, and to the Incubator PMC approval of the release.

+
+
+ Downloading stdcxx Releases +

See the table below for available releases. In the table, the version column indicates the library version. The date column indicates the date the version was released. The file column contains one or more links to the tarball or zip file available for download. The size column is the size of the file in kilobytes. The md5 sum column indicates the MD5 sum for the file and is also a link pointing to the MD5 sum file that can be downloaded. The fixes column contains 3 numbers: the first, Bug Fixes, indicating the number of bugs affecting previous versions that were resolved in the release, the second, Improvements, indicating the number of improvements made in this release with respect to previous releases, and the third, New Features, indicating the number of entire new features implemented in this release. Each non-zero number is a link to the list of the corresponding issues in the bug-tracking database. The comment column contains links to the community vote a pproving the release, and to the Incubator PMC approval of the release.

+
+ + Propchange: stdcxx/site/forrest/src/documentation/content/xdocs/download.xml ------------------------------------------------------------------------------ svn:eol-style = native Propchange: stdcxx/site/forrest/src/documentation/content/xdocs/download.xml ------------------------------------------------------------------------------ svn:keywords = Id Added: stdcxx/site/forrest/src/documentation/content/xdocs/images/group-logo.gif URL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/xdocs/images/group-logo.gif?rev=618441&view=auto ============================================================================== Binary file - no diff available. Propchange: stdcxx/site/forrest/src/documentation/content/xdocs/images/group-logo.gif ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: stdcxx/site/forrest/src/documentation/content/xdocs/images/group.svg URL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/xdocs/images/group.svg?rev=618441&view=auto ============================================================================== --- stdcxx/site/forrest/src/documentation/content/xdocs/images/group.svg (added) +++ stdcxx/site/forrest/src/documentation/content/xdocs/images/group.svg Mon Feb 4 13:20:33 2008 @@ -0,0 +1,82 @@ + + + + + + + + Anteater logo + + + + + + + + + + + + + + + + + + + + + + + + + + + Propchange: stdcxx/site/forrest/src/documentation/content/xdocs/images/group.svg ------------------------------------------------------------------------------ svn:eol-style = native Propchange: stdcxx/site/forrest/src/documentation/content/xdocs/images/group.svg ------------------------------------------------------------------------------ svn:keywords = Id Added: stdcxx/site/forrest/src/documentation/content/xdocs/images/icon.png URL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/xdocs/images/icon.png?rev=618441&view=auto ============================================================================== Binary file - no diff available. Propchange: stdcxx/site/forrest/src/documentation/content/xdocs/images/icon.png ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: stdcxx/site/forrest/src/documentation/content/xdocs/images/project-logo.gif URL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/xdocs/images/project-logo.gif?rev=618441&view=auto ============================================================================== Binary file - no diff available. Propchange: stdcxx/site/forrest/src/documentation/content/xdocs/images/project-logo.gif ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: stdcxx/site/forrest/src/documentation/content/xdocs/images/project.svg URL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/xdocs/images/project.svg?rev=618441&view=auto ============================================================================== --- stdcxx/site/forrest/src/documentation/content/xdocs/images/project.svg (added) +++ stdcxx/site/forrest/src/documentation/content/xdocs/images/project.svg Mon Feb 4 13:20:33 2008 @@ -0,0 +1,82 @@ + + + + + + + + Anteater logo + + + + + + + + + + + + + + + + + + + + + + + + + + + Propchange: stdcxx/site/forrest/src/documentation/content/xdocs/images/project.svg ------------------------------------------------------------------------------ svn:eol-style = native Propchange: stdcxx/site/forrest/src/documentation/content/xdocs/images/project.svg ------------------------------------------------------------------------------ svn:keywords = Id Added: stdcxx/site/forrest/src/documentation/content/xdocs/images/usemap.gif URL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/xdocs/images/usemap.gif?rev=618441&view=auto ============================================================================== Binary file - no diff available. Propchange: stdcxx/site/forrest/src/documentation/content/xdocs/images/usemap.gif ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: stdcxx/site/forrest/src/documentation/content/xdocs/index.xml URL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/xdocs/index.xml?rev=618441&view=auto ============================================================================== --- stdcxx/site/forrest/src/documentation/content/xdocs/index.xml (added) +++ stdcxx/site/forrest/src/documentation/content/xdocs/index.xml Mon Feb 4 13:20:33 2008 @@ -0,0 +1,182 @@ + + + + +
+ Apache C++ Standard Library (STDCXX) +
+ +
+ What is the Apache C++ Standard Library? +

+ The Apache C++ Standard Library project (code name stdcxx, pronounced "standard C++ library", not S-T-D-C-X-X) is a collection of algorithms, containers, iterators, and other fundamental components of every piece of software, implemented as C++ classes, templates, and functions essential for writing C++ programs. +

+

The goal of the Apache C++ Standard Library is to provide a free implementation of the ISO/IEC 14882 international standard for C++ that enables source code portability and consistent behavior of programs across all major hardware implementations, operating systems, and compilers, open source and commercial alike. An additional goal is to achieve maximum implementation efficiency on each platform by taking advantage of platform-specific high-performance facilities and features which are often unique to the type of hardware, the operating system or the compiler. +

+

As the starting point for future efforts, in summer 2005 Rogue Wave Software has contributed its commercial implementation of the C++ Standard Library to the Apache stdcxx project, a proven code base that has been shipping for over a decade and is among the most widely used cross-platform implementations of the library. +

+

The key features of the stdcxx project at the time of submission include: +

+
    +
  • Full conformance to the C++ standard
    • +
  • Complete implementation of the localization library independent of the underlying operating system, including a large set of locale definition files, character set description files, and utility programs to process these files and generate locale databases
    • +
  • User control over strict or permissive conformance checking
    • +
  • Thread-safe implementation of strings, iostreams, and locales
    • +
  • Reference counted basic_string implementation using atomic locking with the ability to switch to a non-reference counted implementation
    • +
  • Excellent runtime performance
    • +
  • Optimized for fast compiles and extremely small executable file sizes
    • +
  • Portable to and fully tested on a large set of operating systems, including AIX, HP-UX, Linux, Solaris, Windows, etc.
    • +
  • Portable to most leading commercial as well as open source compilers
    • +
  • Debugging facilities such as safe iterators, precondition and postcondition checking, and the ability to generate stack traces
    • +
  • Fully documented configuration and build infrastructure
    • +
  • Thorough, well-maintained documentation
    • +
  • Ten years of deployment in the world's most critical enterprise systems
    • +
+
+
+ Objectives +

The long-term objectives of the project include:

+
    +
  • Standards Conformance. Continue to closely track the C++ Standard, as well as any other relevant standards.
    • +
  • Portablity. Continue to provide support for a broad set of platforms (C++ compilers, operating systems, and hardware architectures)
    • +
  • Quality of Implementation. Maintain the current high quality of implementation, which has come to be expected of all Apache projects. This ranges from high runtime efficiency to high space efficiency, to high portability of data (in areas such as localization and internationalization which are typically not specified by the C++ or C standards), to facilitating the portability of program source code.
    • +
+
+
+ Project News +
    +
  • 12/14/2007 STDCXX graduates from the Incubator and becomes a Top Level Project.
    • +
  • 11/29/2007 STDCXX community adds a new committer, Travis Vitek.
    • +
  • 10/29/2007 With the approval of the Incubator PMC, STDCXX 4.2.0 was released.
    • +
  • 10/16/2007 Proposal to graduate STDCXX to a Top Level Project passes the Incubator PMC vote.
    • +
  • 9/5/2007 STDCXX community adds two new committers, Eric (Brad) Lemings and Mark Brown.
    • +
  • 10/11/2006 STDCXX community adds a new committer, Andrew Black.
    • +
  • 8/26/2007 Started tracking project metrics at www.ohloh.net under Apache C++ Standard Library.
    • +
  • 6/1/2007 Started tracking site visitation at Google Analytics under stdcxx. Send an email from your Google Mail account to dev to request access to the account.
    • +
  • 3/26/2007 Tim Triemstra joins the PPMC.
    • +
  • 2/13/2007 Andrew Black and Farid Zaripov join the PPMC.
    • +
  • 10/11/2006 STDCXX community adds a new committer, Andrew Black.
    • +
  • 8/10/2006 STDCXX community adds a new committer, Farid Zaripov.
    • +
  • 1/30/2006 With the approval of the Incubator PMC, STDCXX 4.1.3 was released.
    • +
  • 1/13/2006 STDCXX community adds a new committer, Anton Pevtsov.
    • +
  • 11/25/2005 Windows configuration and build infarstructure committed to Subversion (stdcxx-5).
    • +
  • 9/16/2005 The first snapshot of stdcxx 4.1.2 has been published.
    • +
  • 9/5/2005 The test suite driver committed to Subversion (stdcxx-3).
    • +
  • 9/1/2005 A proposal to publish the first stdcxx snapshot on the stdcxx Web site has passed the community vote.
    • +
  • 8/28/2005 The process of downloading stdcxx files documented on the Download page. (See stdcxx-17).
    • +
  • 8/01/2005 The process of reporting bugs in the stdcxx bug tracking database documented and published on the Bugs page. (See stdcxx-9.)
    • +
  • 7/19/2005 stdcxx project page committed to Subversion. The project status page committed to Subversion.
    • +
  • 7/18/2005 stdcxx sources and documentation committed Subversion.
    • +
  • 5/19/2005 stdcxx project accepted for incubation.
    • +
  • 5/13/2005 stdcxx project proposal submitted to the Incubator mailing list.
    • +
+
+
+ Platforms +

A key stdcxx objective is to facilitate the portability of C++ programs to as many platforms (hardware architectures, operating systems, and compilers) as practical. It is envisaged that the set of platforms will evolve and grow as the project attracts contributors.

+

+ +The project sources initially committed to the Subversion repository +(revision 219596) +are based on Rogue Wave C++ Standard Library version 4.1.0. The list +of platforms to which this version of the project was ported (but +which is expected to grow as the stdcxx project evolves) is:

+
+
+ Project Status +

Stdcxx status reports to the ASF Board of Directors are stored in the status/ subdirectory of the site.

+
+
+ Users +

+Stdcxx Users are Developers with read-only access, i.e., without Commit Access to the stdcxx Codebase who are using the project. +

+

+The mailing list appropriate for discussions of using the stdcxx project is user@stdcxx.apache.org. This is an archived, moderated mailing list open to all subscribers. +You may subscribe by sending a blank email to user-subscribe@stdcxx.apache.org. To obtain additional information about this list send a blank email to user-info@stdcxx.apache.org. +

+ +
+
+ Contributors +

Stdcxx Contributors are Developers without commit (or write) access to the stdcxx codebase who directly or otherwise make improvements to the project codebase, including its Web pages. This includes but is not limited to individuals who respond to questions on the project's mailing lists, review and provide helpful feedback on patches or commits, submit, provide helpful comments on, or triage bug reports, or contribute useful patches of their own. Interested contributors may be voted to become Committers after a period of valuable activity.

+

Because Contributors have read but not write access to stdcxx code repository, they can check stdcxx out and make changes to their local copy of stdcxx files but they cannot check them back in. To get their changes committed, they must follow the process for Submitting Patches.

+

The stdcxx community welcomes new contributors. If you are interested in getting involved, the first thing to do after reading the project Web pages is to subscribe to the dev mailing list and skimming the archives. If you're looking for ideas for where your help might be needed, browse the bug database or simply ask on the maling list. +Committers +

+
+
+ Committers +

Stdcxx Committers are Developers with commit (or write) access to the stdcxx codebase. For safe changes on trunk all stdcxx committers follow the Commit-Then-Review policy (CTR for short). For potentially unsafe changes or any changes to branches all stdcxx committers follow the Review-Then-Commit policy (RTC for short). Whether a change is safe or not is a judgment call that should be made after careful testing of the change on at least two different platforms with two different compilers. The list of current committers in alphabetical order is below:

+

Committers in italics do not yet have a signed Contributor License Agreement on file. This indicates a transient state after a committer has been voted in but their CLA hasn't been received or processed by the foundation. + +An up-to-date list of all Apache committers (or committers-to-be) is being maintained by Jim Jagielski on this page. + +The mailing list used by stdcxx committers for discussions of the maintenance, development, and porting of the stdcxx project is dev@stdcxx.apache.org. This is an archived, moderated mailing list open to all subscribers. You may subscribe by sending a blank email to dev-subscribe@stdcxx.apache.org. +

+
+
+ PMC +

The stdcxx Project Management Committee (PMC) is a group of volunteers responsible for the formal oversight of the stdcxx podling, its management, and for interfacing with the Apache Board of Directors. The members of the stdcxx PMC are:

+

+

The PMC mailing list is private@stdcxx.apache.org. This is a moderated, by-invitation-only mailing list closed to the public. Invited individuals can subscribe by sending a blank email to private-subscribe@stdcxx.apache.org. + +An example of a topic that might be appropriate for this list is a discussion of the merits of a proposed committer. +

+
+
+ Communication + +

+ Communication about the project and all decisions take place on the project's mailing lists. There are a number good reasons why communicating on mailing lists is preferable to other ways of communicating, including private email or instant messaging. Some of the important ones include:

+
    +
  • Unlike communicating in private, mailing lists make it possible for all list subscribers to benefit from the discussion, and provides an opportunity for those who wouldn't be invited to the private discussion to offer their own feedback on the subject.
    • +
  • Unlike Instant Messaging, mailing list make it possible for interested parties to participate asynchronously, regardless of which time zone they are located in.
    • +
  • Unlike private communications, mailing list discussions are archived for future reference, with the archives being easily searchable by anyone interested. Mailing list archives are important not just so that new contributors can learn from past decisions but they are an indispensable tool also for long-time committers when we forget why certain things were done a certain way.
    • +
  • It is the preferred mode of communicating for all Apache projects. See the Communication section of How the ASF works.
    • +
+

+If you choose to contact one of the project committers in private expect to be directed to the mailing lists. +

+
+
+ Mailing Lists +

The following table provides a summary of information about stdcxx mailing lists along with a number of interfaces to their archives. + All lists are moderated. Only subscribers may post. Subscription to private is by invitation of the PMC only. + With one exception, the activity of each list is monitored and can be viewed along with other interesting information on this page maintained by Ken Coar. +

+
+
+ References + + +

A number of excellent design and programming books describe the C++ Standard Library in an approachable way. In addition, besides the required Class Reference, this implementation of the library also includes an extensive User Guide complete with tutorials and example programs. That being said, the ultimate reference to the C++ Standard Library is, of course, the C++ Standard itself (and to a smaller extent, also the C Standard). An electronic copy of the most recent version of the C++ and C standards can be obtained from the ANSI eStandards store.

+
    +
  • INCITS/ISO/IEC 14882-2003 Programming Languages -- C++
    • +
  • INCITS/ISO/IEC 9899-1999 Programming Languages -- C
    • +
  • The C++ Standard Library: A Tutorial and Reference by Nicolai M. Josuttis
    • +
  • Generic Programming and the STL: Using and Extending the C++ Standard Template Library by Matthew H. Austern
    • +
  • Stl Tutorial & Reference Guide: C++ Programming With the Standard Template Library by David R. Musser and Atul Saini
    • +
  • The C++ Standard Template Library by P.J. Plauger, Alexander A. Stepanov, Meng Lee, and David R. Musser
    • +
  • Effective STL: 50 Specific Ways to Improve Your Use of the Standard Template Library by Scott Meyers
    • +
  • Standard C++ IOStreams and Locales: Advanced Programmer's Guide and Reference by Angelika Langer, Klaus Kreft
    • +
+
+ + Propchange: stdcxx/site/forrest/src/documentation/content/xdocs/index.xml ------------------------------------------------------------------------------ svn:eol-style = native Propchange: stdcxx/site/forrest/src/documentation/content/xdocs/index.xml ------------------------------------------------------------------------------ svn:keywords = Id Added: stdcxx/site/forrest/src/documentation/content/xdocs/site.xml URL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/xdocs/site.xml?rev=618441&view=auto ============================================================================== --- stdcxx/site/forrest/src/documentation/content/xdocs/site.xml (added) +++ stdcxx/site/forrest/src/documentation/content/xdocs/site.xml Mon Feb 4 13:20:33 2008 @@ -0,0 +1,62 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + Propchange: stdcxx/site/forrest/src/documentation/content/xdocs/site.xml ------------------------------------------------------------------------------ svn:eol-style = native Propchange: stdcxx/site/forrest/src/documentation/content/xdocs/site.xml ------------------------------------------------------------------------------ svn:keywords = Id Added: stdcxx/site/forrest/src/documentation/content/xdocs/tabs.xml URL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/xdocs/tabs.xml?rev=618441&view=auto ============================================================================== --- stdcxx/site/forrest/src/documentation/content/xdocs/tabs.xml (added) +++ stdcxx/site/forrest/src/documentation/content/xdocs/tabs.xml Mon Feb 4 13:20:33 2008 @@ -0,0 +1,39 @@ + + + + + + + + + Propchange: stdcxx/site/forrest/src/documentation/content/xdocs/tabs.xml ------------------------------------------------------------------------------ svn:eol-style = native Propchange: stdcxx/site/forrest/src/documentation/content/xdocs/tabs.xml ------------------------------------------------------------------------------ svn:keywords = Id Added: stdcxx/site/forrest/src/documentation/resources/images/Thumbs.db URL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/resources/images/Thumbs.db?rev=618441&view=auto ============================================================================== Binary file - no diff available. Propchange: stdcxx/site/forrest/src/documentation/resources/images/Thumbs.db ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: stdcxx/site/forrest/src/documentation/resources/images/stdcxx.png URL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/resources/images/stdcxx.png?rev=618441&view=auto ============================================================================== Binary file - no diff available. Propchange: stdcxx/site/forrest/src/documentation/resources/images/stdcxx.png ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: stdcxx/site/forrest/src/documentation/resources/schema/catalog.xcat URL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/resources/schema/catalog.xcat?rev=618441&view=auto ============================================================================== --- stdcxx/site/forrest/src/documentation/resources/schema/catalog.xcat (added) +++ stdcxx/site/forrest/src/documentation/resources/schema/catalog.xcat Mon Feb 4 13:20:33 2008 @@ -0,0 +1,29 @@ + + + + + + + + + + Propchange: stdcxx/site/forrest/src/documentation/resources/schema/catalog.xcat ------------------------------------------------------------------------------ svn:eol-style = native Propchange: stdcxx/site/forrest/src/documentation/resources/schema/catalog.xcat ------------------------------------------------------------------------------ svn:keywords = Id