stdcxx-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From se...@apache.org
Subject svn commit: r584901 [1/2] - in /incubator/stdcxx/branches/4.2.0/doc: stdlibref/ stdlibug/
Date Mon, 15 Oct 2007 20:36:05 GMT
Author: sebor
Date: Mon Oct 15 13:36:02 2007
New Revision: 584901

URL: http://svn.apache.org/viewvc?rev=584901&view=rev
Log:
2007-10-15  Martin Sebor  <sebor@roguewave.com>

	* branches/4.2.0/doc: Merged the latest trunk.

Removed:
    incubator/stdcxx/branches/4.2.0/doc/stdlibref/contact.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibref/copyright.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-6.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-7.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/contact.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/copyright.html
Modified:
    incubator/stdcxx/branches/4.2.0/doc/stdlibref/1-1.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibref/locale.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibref/localedefutility.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibref/noframes.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibref/valarray.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-1.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-2.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-3.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-4.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-5.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/1.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/16-1.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/16-3.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/17-2.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/18-3.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/22-4.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/22-7.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/24-2.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/24-4.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/25-5.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/27-3.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/27-4.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/28-3.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/30-2.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/32-5.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/33-3.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/36-3.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/39-1.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/40-5.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/41-2.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/42-1.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/II.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/booktoc.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/frames-contents-all.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/noframes.html
    incubator/stdcxx/branches/4.2.0/doc/stdlibug/tindex.html

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibref/1-1.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibref/1-1.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibref/1-1.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibref/1-1.html Mon Oct 15 13:36:02 2007
@@ -25,7 +25,7 @@
 <BODY BGCOLOR=#FFFFFF>
 <A HREF="1.html"><IMG SRC="images/bprev.gif" WIDTH=20 HEIGHT=21 ALT="Previous file" BORDER=O></A><A HREF="noframes.html"><IMG SRC="images/btop.gif" WIDTH=56 HEIGHT=21 ALT="Top of Document" BORDER=O></A><A HREF="booktoc.html"><IMG SRC="images/btoc.gif" WIDTH=56 HEIGHT=21 ALT="Contents" BORDER=O></A><A HREF="tindex.html"><IMG SRC="images/bindex.gif" WIDTH=56 HEIGHT=21 ALT="Index page" BORDER=O></A><A HREF="1-2.html"><IMG SRC="images/bnext.gif" WIDTH=25 HEIGHT=21 ALT="Next file" BORDER=O></A><DIV CLASS="DOCUMENTNAME"><B>Apache C++ Standard Library Reference Guide</B></DIV>
 <H2>1.1 Contents of Entries</H2>
-<P>This reference guide is an alphabetical listing of the header files, classes, containers, algorithms, iterators, and other constructs of the C++ Standard Library Module of SourcePro Core. The entry for each <I>class</I> includes:</P>
+<P>This reference guide is an alphabetical listing of the header files, classes, containers, algorithms, iterators, and other constructs of the Apache C++ Standard Library Module. The entry for each <I>class</I> includes:</P>
 <UL>
 <LI><P CLASS="LIST">An illustration showing the inheritance hierarchy, or the general category to which the class belongs</P></LI>
 <LI><P CLASS="LIST">A brief summary of the class functionality</P></LI>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibref/locale.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibref/locale.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibref/locale.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibref/locale.html Mon Oct 15 13:36:02 2007
@@ -23,7 +23,7 @@
 <TITLE>locale</TITLE>
 <LINK REL=StyleSheet HREF="../rw.css" TYPE="text/css" TITLE="Apache stdcxx Stylesheet"></HEAD>
 <BODY BGCOLOR=#FFFFFF>
-<A HREF="locale-h.html"><IMG SRC="images/bprev.gif" WIDTH=20 HEIGHT=21 ALT="Previous file" BORDER=O></A><A HREF="noframes.html"><IMG SRC="images/btop.gif" WIDTH=56 HEIGHT=21 ALT="Top of Document" BORDER=O></A><A HREF="booktoc.html"><IMG SRC="images/btoc.gif" WIDTH=56 HEIGHT=21 ALT="Contents" BORDER=O></A><A HREF="tindex.html"><IMG SRC="images/bindex.gif" WIDTH=56 HEIGHT=21 ALT="Index page" BORDER=O></A><A HREF="localeutility.html"><IMG SRC="images/bnext.gif" WIDTH=25 HEIGHT=21 ALT="Next file" BORDER=O></A><DIV CLASS="DOCUMENTNAME"><B>Apache C++ Standard Library Reference Guide</B></DIV>
+<A HREF="locale-h.html"><IMG SRC="images/bprev.gif" WIDTH=20 HEIGHT=21 ALT="Previous file" BORDER=O></A><A HREF="noframes.html"><IMG SRC="images/btop.gif" WIDTH=56 HEIGHT=21 ALT="Top of Document" BORDER=O></A><A HREF="booktoc.html"><IMG SRC="images/btoc.gif" WIDTH=56 HEIGHT=21 ALT="Contents" BORDER=O></A><A HREF="tindex.html"><IMG SRC="images/bindex.gif" WIDTH=56 HEIGHT=21 ALT="Index page" BORDER=O></A><A HREF="localeutility.html"><IMG SRC="images/bnext.gif" WIDTH=20 HEIGHT=21 ALT="Next file" BORDER=O></A><DIV CLASS="DOCUMENTNAME"><B>Apache C++ Standard Library Reference Guide</B></DIV>
 <H2>locale</H2>
 <P><B>Library:</B>&nbsp;&nbsp;<A HREF="2-6.html">Localization</A></P>
 
@@ -382,7 +382,7 @@
 </UL>
 
 <A NAME="sec12"><H3>Included Locales</H3></A>
-<P><A HREF="locale.html#Table&nbsp;21">Table&nbsp;21</A> lists the locale definition files that correspond with the the locales of the C++ Standard Library Module. The names conform to ISO 639:1998, the <I>Code for the Representation of Names of Languages</I>, and ISO 3166, the <I>Country Names and Codes</I>. The Default Codeset gives the name of the codeset or the encoding the locales are designed to be encoded in. The names follow those outlined by IANA in its <I>Assigned Character Set Names</I>. In addition to the listed codeset, each locale can be encoded in UTF-8, and may be able to use other encodings as well.   </P>
+<P><A HREF="locale.html#Table&nbsp;21">Table&nbsp;21</A> lists the locale definition files that correspond with the the locales of the Apache C++ Standard Library. The names conform to ISO 639:1998, the <I>Code for the Representation of Names of Languages</I>, and ISO 3166, the <I>Country Names and Codes</I>. The Default Codeset gives the name of the codeset or the encoding the locales are designed to be encoded in. The names follow those outlined by IANA in its <I>Assigned Character Set Names</I>. In addition to the listed codeset, each locale can be encoded in UTF-8, and may be able to use other encodings as well.   </P>
 <H4><A NAME="Table&nbsp;21">Table&nbsp;21: Locale definition files&nbsp;</A></H4>
 <TABLE BORDER="1" CELLPADDING="3" CELLSPACING="3">
 <tr><td valign=top><B>Locale Name</B>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibref/localedefutility.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibref/localedefutility.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibref/localedefutility.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibref/localedefutility.html Mon Oct 15 13:36:02 2007
@@ -23,7 +23,7 @@
 <TITLE>localedef utility</TITLE>
 <LINK REL=StyleSheet HREF="../rw.css" TYPE="text/css" TITLE="Apache stdcxx Stylesheet"></HEAD>
 <BODY BGCOLOR=#FFFFFF>
-<A HREF="localeutility.html"><IMG SRC="images/bprev.gif" WIDTH=20 HEIGHT=21 ALT="Previous file" BORDER=O></A><A HREF="noframes.html"><IMG SRC="images/btop.gif" WIDTH=56 HEIGHT=21 ALT="Top of Document" BORDER=O></A><A HREF="booktoc.html"><IMG SRC="images/btoc.gif" WIDTH=56 HEIGHT=21 ALT="Contents" BORDER=O></A><A HREF="tindex.html"><IMG SRC="images/bindex.gif" WIDTH=56 HEIGHT=21 ALT="Index page" BORDER=O></A><A HREF="logic-error.html"><IMG SRC="images/bnext.gif" WIDTH=25 HEIGHT=21 ALT="Next file" BORDER=O></A><DIV CLASS="DOCUMENTNAME"><B>Apache C++ Standard Library Reference Guide</B></DIV>
+<A HREF="localeutility.html"><IMG SRC="images/bprev.gif" WIDTH=20 HEIGHT=21 ALT="Previous file" BORDER=O></A><A HREF="noframes.html"><IMG SRC="images/btop.gif" WIDTH=56 HEIGHT=21 ALT="Top of Document" BORDER=O></A><A HREF="booktoc.html"><IMG SRC="images/btoc.gif" WIDTH=56 HEIGHT=21 ALT="Contents" BORDER=O></A><A HREF="tindex.html"><IMG SRC="images/bindex.gif" WIDTH=56 HEIGHT=21 ALT="Index page" BORDER=O></A><A HREF="logic-error.html"><IMG SRC="images/bnext.gif" WIDTH=20 HEIGHT=21 ALT="Next file" BORDER=O></A><DIV CLASS="DOCUMENTNAME"><B>Apache C++ Standard Library Reference Guide</B></DIV>
 <H2>localedef utility</H2><PRE><HR><B><I>Utility Program</I></B><HR></PRE>
 
 <UL>
@@ -168,7 +168,7 @@
 <P>Unless the <SAMP>-i</SAMP> option is used, <SAMP>localedef</SAMP> reads the locale definition from <SAMP>stdin</SAMP>. Otherwise, <SAMP>localedef</SAMP> reads the locale definition from the filename specified with the <SAMP>-i</SAMP> option. The utility also attempts to read files named by any copy directives that appear in the locale definition. <SAMP>localedef</SAMP> reads character set descriptions from the files specified with the <SAMP>-f</SAMP> option.</P>
 <P>The required format of the character set description file follows that described in section 6.4, Character Set Description File, of IEEE Std 1003.1-2001.</P>
 <P>The required format of the locale definition file follows that described in section 7.3, Locale Definition, of IEEE Std 1003.1-2001. </P>
-<P>Any files that conform to the required format can be used with <SAMP>localedef</SAMP> to produce binary locale database files suitable for use with the C++ Standard Library Module.</P>
+<P>Any files that conform to the required format can be used with <SAMP>localedef</SAMP> to produce binary locale database files suitable for use with the Apache C++ Standard Library.</P>
 <P>A limited number of character set description files and locale definition files in the conforming format can be purchased from The Open Group. See   <SAMP>http://www.opengroup.org/pubs/catalog/lo.htm</SAMP>.</P>
 <P>Character set description files and locale definition files in an extended format can be obtained without charge from the JTC1/SC22/WG15 -- POSIX pages at <SAMP>ftp://dkuug.dk/i18n/WG15-collection/</SAMP>. These files are distributed with the Apache C++ Standard Library sources.</P>
 <P>Additionally, the <SAMP>localedef</SAMP> utility also accepts files in an extended format used by GNU C library, glibc 2<br><SAMP>(http://www.gnu.org/software/libc/libc.html)</SAMP>. The locale definition files that accompany glibc 2.2.5 are distributed with the Apache C++ Standard Library sources. </P>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibref/noframes.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibref/noframes.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibref/noframes.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibref/noframes.html Mon Oct 15 13:36:02 2007
@@ -20,11 +20,11 @@
 
 <HTML>
 <HEAD>
-<TITLE>C++ Standard Library Module Reference Guide</TITLE>
+<TITLE>Apache C++ Standard Library Reference Guide</TITLE>
 <LINK REL=StyleSheet HREF="../rw.css" TYPE="text/css" TITLE="Apache stdcxx Stylesheet"></HEAD>
 <BODY BGCOLOR=#FFFFFF>
-<H1>C++ Standard Library Module Reference Guide</H1>
-<P>Welcome to the <I>C++ Standard Library Module Reference Guide</I>.</P>
+<H1>Apache C++ Standard Library Reference Guide</H1>
+<P>Welcome to the <I>Apache C++ Standard Library Reference Guide</I>.</P>
 <P>Here are several ways you can access the information in this document:</P>
 <UL>
 <LI>Hypertext lists showing the classes and other elements described in this document, arranged

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibref/valarray.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibref/valarray.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibref/valarray.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibref/valarray.html Mon Oct 15 13:36:02 2007
@@ -857,34 +857,50 @@
 //  valarray.cpp
 //
 
-#include &lt;valarray.h&gt;   // for valarray stream inserter
-#include &lt;iostream&gt;     // for cout, endl
+#include &lt;cstddef&gt;      // for size_t
+#include &lt;iostream&gt;     // for cout
+#include &lt;valarray&gt;     // for valarray
+
+#include &lt;examples.h&gt;
+
+
+template &lt;class T&gt; 
+inline std::ostream&
+operator&lt;&lt; (std::ostream &amp;out, const std::valarray&lt;T&gt; &amp;v)
+{
+    out &lt;&lt; '[';
+
+    for (std::size_t i = 0; i &lt; v.size (); ++i) {
+        out &lt;&lt; v [i];
+        if (i &lt; v.size () - 1)
+            out &lt;&lt; ',';
+    }
+
+    return out &lt;&lt; ']';
+}
+
 
 int main ()
 {
-  const int ibuf[]  = { 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 };  
-  const int ibuf2[] = { 10, 11, 12, 13, 14, 
-                        15, 16, 17, 18, 19 };
+    const int ibuf[]  = { 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 };  
+    const int ibuf2[] = { 10, 11, 12, 13, 14, 15, 16, 17, 18, 19 };  
 
-  // create 2 valarrays of ints
-  std::valarray&lt;int&gt; vi (ibuf, sizeof ibuf / sizeof *ibuf);
-  std::valarray&lt;int&gt; vi2 (ibuf2, sizeof ibuf2 / sizeof *ibuf2);
+    // create 2 valarrays of ints
+    std::valarray&lt;int&gt; vi (ibuf, sizeof ibuf / sizeof *ibuf);
+    std::valarray&lt;int&gt; vi2 (ibuf2, sizeof ibuf2 / sizeof *ibuf2);
 
-  // print them out
-  std::cout &lt;&lt; vi  &lt;&lt; std::endl 
-            &lt;&lt; vi2 &lt;&lt; std::endl;
+    // print them out
+    std::cout &lt;&lt; vi &lt;&lt; '\n' &lt;&lt; vi2 &lt;&lt; '\n';
 
-  vi += vi2;
-  vi2 *= 2;
+    vi += vi2;
+    vi2 *= 2;
 
-  std::valarray&lt;int&gt; vi3 = vi2 % vi;
+    std::valarray&lt;int&gt; vi3 = vi2 % vi;
 
-  // print them out again
-  std::cout &lt;&lt; vi  &lt;&lt; std::endl 
-            &lt;&lt; vi2 &lt;&lt; std::endl 
-            &lt;&lt; vi3 &lt;&lt; std::endl;
+    // print them out again
+    std::cout &lt;&lt; vi &lt;&lt; '\n' &lt;&lt; vi2 &lt;&lt; '\n' &lt;&lt; vi3 &lt;< '\n';
 
-  return 0;
+    return 0;
 }
 
 

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-1.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-1.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-1.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-1.html Mon Oct 15 13:36:02 2007
@@ -25,7 +25,7 @@
 <BODY BGCOLOR=#FFFFFF>
 <A HREF="1.html"><IMG SRC="images/bprev.gif" WIDTH=20 HEIGHT=21 ALT="Previous file" BORDER=O></A><A HREF="noframes.html"><IMG SRC="images/btop.gif" WIDTH=56 HEIGHT=21 ALT="Top of Document" BORDER=O></A><A HREF="booktoc.html"><IMG SRC="images/btoc.gif" WIDTH=56 HEIGHT=21 ALT="Contents" BORDER=O></A><A HREF="tindex.html"><IMG SRC="images/bindex.gif" WIDTH=56 HEIGHT=21 ALT="Index page" BORDER=O></A><A HREF="1-2.html"><IMG SRC="images/bnext.gif" WIDTH=25 HEIGHT=21 ALT="Next file" BORDER=O></A><DIV CLASS="DOCUMENTNAME"><B>Apache C++ Standard Library User's Guide</B></DIV>
 <H2>1.1 Welcome</H2>
-<P>Congratulations on choosing the Apache C++ Standard Library, developed and donated to the Apache Software Foundation by <a href="www.roguewave.com">Rogue Wave Software</a>. This module is part of  SourcePro Core, an extensive set of fundamental C++ components. You can use this product with confidence: it is based on the final standard for the C++ language and library ratified in 1998 by the American National Standards Institute (ANSI) and the International Standards Organization (ISO).</P>
+<P>Congratulations on choosing the Apache C++ Standard Library, developed and donated to the Apache Software Foundation by <a href="http://www.roguewave.com">Rogue Wave Software</a>. You can use this product with confidence: it is based on the final standard for the C++ language and library ratified in 1998 by the American National Standards Institute (ANSI) and the International Standards Organization (ISO).</P>
 <A NAME="idx1"><!></A>
 <P>Since its development by Dr. Bjarne Stroustrup in the 1980s, the C++ language has been widely used by professional programmers for the world's big, complex applications in telecommunications, finance, business, embedded systems, and computer-aided design. The final standardization of the C++ library now makes it easier to learn C++ and to use it across a wide variety of platforms. </P>
 <P>Standardization improves portability and stability. You can build reliable applications faster, and maintain them with less cost and effort, using the C++ Standard Library.</P>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-2.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-2.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-2.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-2.html Mon Oct 15 13:36:02 2007
@@ -45,10 +45,6 @@
 <P>The STL portion of the C++ Standard Library is not object-oriented. If you are accustomed to the benefits of object-oriented programming, their absence may necessitate some adjustment. Encapsulation of data and functionality in objects is a hallmark of object-oriented programming. In the C++ Standard Library, however, the data structures are separate from the algorithms you use to manipulate them.</P>
 <P>This feature can provide a number of advantages, such as smaller source code, and the flexibility of using algorithms with C++ pointers and arrays as well as conventional objects. It can also lead to more efficient coding and faster execution, since it creates a direct, nuts-and-bolts approach to solving problems.</P>
 <P>The main disadvantage of using the C++ Standard Library directly is increased risk of error. For example, the library's iterators must not be mismatched or invalidated, and iterators in multithreaded environments should be wrapped before being shared among threads. The templates can cause less precise diagnostics, and code that grows unexpectedly large. Experience with the library and your own compiler will help diminish these problems.</P>
-<A NAME="123"><H3>1.2.3 Relationship to the Essential Tools Module</H3></A>
-<A NAME="idx4"><!></A>
-<P>This implementation of the C++ Standard Library is certified for use with the  Essential Tools Module of SourcePro Core, which encapsulates the C++ Standard Library with an object-oriented interface. Used together, the Essential Tools and C++ Standard Library Modules are designed to provide the benefits of both low-level generic programming and object-orientation. </P>
-<P>The Essential Tools Module also contains features not included in the standard, such as time, date, and regular expression classes, enhanced strings, hash containers, object persistence, and virtual streams. The Essential Networking Module of SourcePro Net extends the functionality of the Essential Tools Module with classes for network programming. For some programming tasks, you may find it easier and more convenient to use the Essential Tools and Essential Networking Modules without accessing the C++ Standard Library directly. </P>
 
 <BR>
 <HR>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-3.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-3.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-3.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-3.html Mon Oct 15 13:36:02 2007
@@ -34,7 +34,7 @@
 </B><HR></BLOCKQUOTE>
 <P>In the <I>User's Guide</I>, we draw your attention to places in the code where this might be a problem. If your vendor is still in the process of meeting the standard, some of the techniques demonstrated in this <I>User's Guide</I> may not work. We include them anyway to demonstrate the full range of capabilities of the standard C++ language. Compilers will catch up, and this guide will be more useful to you if it is as complete as possible.</P>
 <A NAME="132"><H3>1.3.2 The std Namespace</H3></A>
-<P>Everything in the C++ Standard Library Module is contained in the <SAMP>std</SAMP> namespace. You must specify a <SAMP>using</SAMP> directive or explicitly scope any name from the library.</P>
+<P>Everything in the Apache C++ Standard Library is contained in the <SAMP>std</SAMP> namespace. You must specify a <SAMP>using</SAMP> directive or explicitly scope any name from the library.</P>
 <P>To use the <B><I><A HREF="../stdlibref/vector.html">vector</A></I></B> class, for example, you could include one of the following <SAMP>using</SAMP> directives:</P>
 
 <UL><PRE>
@@ -50,7 +50,7 @@
 std::vector&lt;int&gt; v; 
 </PRE></UL>
 <BLOCKQUOTE><HR><B>
-NOTE -- To enhance this manual's readability,  namespace scoping is usually omitted in the text. You should assume that everything in the C++ Standard Library Module is scoped in namespace <SAMP>std</SAMP> unless otherwise stated.
+NOTE -- To enhance this manual's readability,  namespace scoping is usually omitted in the text. You should assume that everything in the Apache C++ Standard Library is scoped in namespace <SAMP>std</SAMP> unless otherwise stated.
 </B><HR></BLOCKQUOTE>
 
 <BR>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-4.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-4.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-4.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-4.html Mon Oct 15 13:36:02 2007
@@ -27,38 +27,28 @@
 <H2>1.4 Documentation Overview</H2>
 <A NAME="141"><H3>1.4.1 Locations of Online Documentation</H3></A>
 <A NAME="idx5"><!></A>
-<P>To help you learn to use the <B>C++ Standard Library Module</B> quickly and effectively, Apache C++ Standard Library comes with the documentation described in <A HREF="1-4.html#Table&nbsp;1">Table&nbsp;1</A>. </P>
+<P>To help you learn to use the <B>Apache C++ Standard Library</B> quickly and effectively, the library comes with the documentation described in <A HREF="1-4.html#Table&nbsp;1">Table&nbsp;1</A>. </P>
 <P><B>All Apache C++ Standard Library documentation is installed online when you install your product. In addition, printed copies of user's guides may be purchased from your sales representative. </B></P>
-<P><B>For easiest access to the Apache C++ Standard Library online documentation, open the file </B><SAMP><A HREF="../../index.html" TARGET="_top"><I>buildspace</I>\docs\index.html</A></SAMP><B> with your favorite browser, and follow the links to the documents you need.</B></P>
-<P>Online documentation for the C++ Standard Library Module is available at the locations shown in <A HREF="1-4.html#Table&nbsp;1">Table&nbsp;1</A>.</P>
+<P><B>For easiest access to the Apache C++ Standard Library online documentation, open the file </B><SAMP><A HREF="../../index.html" TARGET="_top"><I>${TOPDIR}</I>/doc/index.html</A></SAMP><B> with your favorite browser, and follow the links to the documents you need.</B></P>
+<P>Online documentation for the Apache C++ Standard Library is available at the locations shown in <A HREF="1-4.html#Table&nbsp;1">Table&nbsp;1</A>.</P>
 <A NAME="idx6"><!></A>
 <H4><A NAME="Table&nbsp;1">Table&nbsp;1: Locations of online documentation&nbsp;</A></H4>
 <TABLE BORDER="1" CELLPADDING="3" CELLSPACING="3">
 <tr><td valign=top><B>Document Format</B>
 </td><td valign=top><B>Location</B>
 </td></tr>
-<tr><td valign=top><P CLASS="TABLE">readme file</P>
-</td><td valign=top><P CLASS="TABLE"><SAMP><I>buildspace</I></SAMP><SAMP>\docs\readmes\sourcepro-core\stdlib\readme.txt</SAMP></P>
+<tr><td valign=top><P CLASS="TABLE">plain text</P>
+</td><td valign=top><P CLASS="TABLE"><SAMP><I>${TOPDIR}</I></SAMP><SAMP>/README</SAMP></P>
 </td></tr>
-<tr><td valign=top><P CLASS="TABLE">HTML documentation</P>
+<tr><td valign=top><P CLASS="TABLE">HTML</P>
 </td><td valign=top><P CLASS="TABLE">Single-point access to Apache C++ Standard Library HTML documentation:</P>
-<P CLASS="TABLE"><SAMP><A HREF="../../index.html" TARGET="_top"><I>buildspace</I>\docs\index.html</A></SAMP></P>
-<P CLASS="TABLE">SourcePro documentation:</P>
-<P CLASS="TABLE"><I>Introduction to SourcePro C++:</I> <SAMP><A HREF="../startug/index.html" TARGET="_top"><I>buildspace</I>\docs\html\startug\index.html</A></SAMP></P>
-<P CLASS="TABLE">C++ Standard Library Module documentation:</P>
-<P CLASS="TABLE"><I>User's Guide:</I> <SAMP><A HREF="../stdlibug/index.html" TARGET="_top"><I>buildspace</I>\docs\html\stdlibug\index.html</A></SAMP></P>
-<P CLASS="TABLE"><I>Reference Guide:</I> <SAMP><A HREF="../stdlibref/index.html" TARGET="_top"><I>buildspace</I>\docs\html\stdlibref\index.html</A></SAMP></P>
-<P CLASS="TABLE">RCB documentation:</P>
-<P CLASS="TABLE"><I>Installing and Building Your SourcePro C++ Products:</I> <SAMP><A HREF="../rcbug/index.html" TARGET="_top"><I>buildspace</I>\docs\html\rcbug\index.html</A></SAMP></P>
-<P CLASS="TABLE"><I>Building Your Applications: </I><SAMP><A HREF="../rcbbd/index.html" TARGET="_top"><I>buildspace</I>\docs\html\rcbbd\index.html</A></SAMP></P>
+<P CLASS="TABLE"><SAMP><A HREF="../../index.html" TARGET="_top"><I>${TOPDIR}</I>/doc/index.html</A></SAMP></P>
+<P CLASS="TABLE">Apache C++ Standard Library documentation:</P>
+<P CLASS="TABLE"><I>User's Guide:</I> <SAMP><A HREF="../stdlibug/index.html" TARGET="_top"><I>${TOPDIR}</I>/doc/stdlibug/index.html</A></SAMP></P>
+<P CLASS="TABLE"><I>Reference Guide:</I> <SAMP><A HREF="../stdlibref/index.html" TARGET="_top"><I>${TOPDIR}</I>/doc/stdlibref/index.html</A></SAMP></P>
 </td></tr>
-<tr><td valign=top><P CLASS="TABLE">PDF (user's guides only)</P>
-</td><td valign=top><P CLASS="TABLE"><SAMP><I>buildspace</I></SAMP><SAMP>\docs\pdf\startug.pdf</SAMP></P>
-<P CLASS="TABLE"><SAMP><I>buildspace</I></SAMP><SAMP>\docs\pdf\rcbug.pdf</SAMP></P>
-<P CLASS="TABLE"><SAMP><I>buildspace</I></SAMP><SAMP>\docs\pdf\rcbbd.pdf</SAMP></P>
-</td></tr>
-<tr><td valign=top><P CLASS="TABLE">examples</P>
-</td><td valign=top><P CLASS="TABLE"><SAMP><I>buildspace</I></SAMP><SAMP>\examples\stdlib</SAMP></P>
+<tr><td valign=top><P CLASS="TABLE">C++ source</P>
+</td><td valign=top><P CLASS="TABLE"><SAMP><I>${TOPDIR}</I></SAMP><SAMP>/examples</SAMP></P>
 </td></tr>
 </TABLE>
 

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-5.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-5.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-5.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/1-5.html Mon Oct 15 13:36:02 2007
@@ -23,7 +23,7 @@
 <TITLE>About This Manual</TITLE>
 <LINK REL=StyleSheet HREF="../rw.css" TYPE="text/css" TITLE="Apache stdcxx Stylesheet"></HEAD>
 <BODY BGCOLOR=#FFFFFF>
-<A HREF="1-4.html"><IMG SRC="images/bprev.gif" WIDTH=20 HEIGHT=21 ALT="Previous file" BORDER=O></A><A HREF="noframes.html"><IMG SRC="images/btop.gif" WIDTH=56 HEIGHT=21 ALT="Top of Document" BORDER=O></A><A HREF="booktoc.html"><IMG SRC="images/btoc.gif" WIDTH=56 HEIGHT=21 ALT="Contents" BORDER=O></A><A HREF="tindex.html"><IMG SRC="images/bindex.gif" WIDTH=56 HEIGHT=21 ALT="Index page" BORDER=O></A><A HREF="1-6.html"><IMG SRC="images/bnext.gif" WIDTH=25 HEIGHT=21 ALT="Next file" BORDER=O></A><DIV CLASS="DOCUMENTNAME"><B>Apache C++ Standard Library User's Guide</B></DIV>
+<A HREF="1-4.html"><IMG SRC="images/bprev.gif" WIDTH=20 HEIGHT=21 ALT="Previous file" BORDER=O></A><A HREF="noframes.html"><IMG SRC="images/btop.gif" WIDTH=56 HEIGHT=21 ALT="Top of Document" BORDER=O></A><A HREF="booktoc.html"><IMG SRC="images/btoc.gif" WIDTH=56 HEIGHT=21 ALT="Contents" BORDER=O></A><A HREF="tindex.html"><IMG SRC="images/bindex.gif" WIDTH=56 HEIGHT=21 ALT="Index page" BORDER=O></A><A HREF="II.html"><IMG SRC="images/bnext.gif" WIDTH=25 HEIGHT=21 ALT="Next file" BORDER=O></A><DIV CLASS="DOCUMENTNAME"><B>Apache C++ Standard Library User's Guide</B></DIV>
 <H2>1.5 About This Manual</H2>
 <A NAME="151"><H3>1.5.1 Assumptions</H3></A>
 <P>This manual assumes that you are familiar with the basic features of the C++ programming language. If you are new to C++, you may want to start with an introductory text, such as <I>The C++ Programming Language</I> by Bjarne Stroustrup (Addison-Wesley, 1997).</P>
@@ -51,7 +51,7 @@
 </td></tr>
 <tr><td valign=top><P CLASS="TABLE"><I>italic</I></P>
 </td><td valign=top><P CLASS="TABLE">Conventional uses such as emphasis, titles, and new terms.</P>
-</td><td valign=top><P CLASS="TABLE">A comparison function object is...</P>
+</td><td valign=top><P CLASS="TABLE">A <I>comparison function object</I> is...</P>
 </td></tr>
 <tr><td valign=top><P CLASS="TABLE"><B>bold</B></P>
 </td><td valign=top><P CLASS="TABLE">Conventional uses such as <B>emphasis</B>.</P>
@@ -68,10 +68,10 @@
 <A NAME="153"><H3>1.5.3 Organization</H3></A>
 <P>This manual is organized into eight parts:</P>
 <UL>
-<LI><P CLASS="LIST"><B><A HREF="I.html">Part&nbsp;I, "Introduction,"</A></B> provides overviews of the product, the documentation, and this manual, <I>The C++ Standard Library Module User's Guide</I>. </P></LI>
+<LI><P CLASS="LIST"><B><A HREF="I.html">Part&nbsp;I, "Introduction,"</A></B> provides overviews of the product, the documentation, and this manual, <I>The Apache C++ Standard Library User Guide</I>. </P></LI>
 <LI><P CLASS="LIST"><B><A HREF="II.html">Part&nbsp;II, "Fundamentals,"</A></B> explains the fundamental C++ Standard Library concepts of iterators, functions, and predicates.</P></LI>
-<LI><P CLASS="LIST"><B><A HREF="III.html">Part&nbsp;III, "Containers,"</A></B> gives an overview of the data structures called <I>containers</I>, and devotes a chapter to describing each container in detail with an example. </P></LI>
-<LI><P CLASS="LIST"><B><A HREF="IV.html">Part&nbsp;IV, "Algorithms,"</A></B> deals with the algorithms, devoting one chapter to the generic algorithms, and another to the generic algorithms specific to ordered collections. Within the two algorithm chapters, each kind of algorithm is explained in its own section with an example and a reference to the file containing the complete source code. </P></LI>
+<LI><P CLASS="LIST"><B><A HREF="III.html">Part&nbsp;III, "Containers,"</A></B> gives an overview of the data structures called <I>containers</I>, and devotes a chapter to describing each container in detail, with an example. </P></LI>
+<LI><P CLASS="LIST"><B><A HREF="IV.html">Part&nbsp;IV, "Algorithms,"</A></B> deals with the algorithms, devoting one chapter to the generic algorithms, and another to the generic algorithms specific to ordered collections. Within the two algorithm chapters, each kind of algorithm is explained in its own section, with an example and a reference to the file containing the complete source code. </P></LI>
 <LI><P CLASS="LIST"><B><A HREF="V.html">Part&nbsp;V, "Special Techniques,"</A></B> describes techniques such as using allocators, building containers and generic algorithms, using the traits technique, and dealing with exceptions.</P></LI>
 <LI><P CLASS="LIST"><B><A HREF="VI.html">Part&nbsp;VI, "Special Classes,"</A></B> devotes a chapter to each of the four unique classes <B><I><A HREF="../stdlibref/auto-ptr.html">auto_ptr</A></I></B>, <B><I><A HREF="../stdlibref/complex.html">complex</A></I></B>, <B><I><A HREF="../stdlibref/numeric-limits.html">numeric_limits</A></I></B>, and <B><I><A HREF="../stdlibref/valarray.html">valarray</A></I></B>.</P></LI>
 <LI><P CLASS="LIST"><B><A HREF="VII.html">Part&nbsp;VII, "Locales,"</A></B> describes the basics of internationalization.  It explains the differences between the C locale and the C++ locale. It defines a C++ locale and a facet, and tells how locales are created, composed, used, and replaced. It includes a complex example of a user-defined facet, which demonstrates how facets can be built and used in conjunction with iostreams.</P></LI>
@@ -83,7 +83,7 @@
 
 <BR>
 <HR>
-<A HREF="1-4.html"><IMG SRC="images/bprev.gif" WIDTH=20 HEIGHT=21 ALT="Previous file" BORDER=O></A><A HREF="noframes.html"><IMG SRC="images/btop.gif" WIDTH=56 HEIGHT=21 ALT="Top of Document" BORDER=O></A><A HREF="booktoc.html"><IMG SRC="images/btoc.gif" WIDTH=56 HEIGHT=21 ALT="Contents" BORDER=O></A><A HREF="tindex.html"><IMG SRC="images/bindex.gif" WIDTH=56 HEIGHT=21 ALT="Index page" BORDER=O></A><A HREF="1-6.html"><IMG SRC="images/bnext.gif" WIDTH=20 HEIGHT=21 ALT="Next file" BORDER=O></A>
+<A HREF="1-4.html"><IMG SRC="images/bprev.gif" WIDTH=20 HEIGHT=21 ALT="Previous file" BORDER=O></A><A HREF="noframes.html"><IMG SRC="images/btop.gif" WIDTH=56 HEIGHT=21 ALT="Top of Document" BORDER=O></A><A HREF="booktoc.html"><IMG SRC="images/btoc.gif" WIDTH=56 HEIGHT=21 ALT="Contents" BORDER=O></A><A HREF="tindex.html"><IMG SRC="images/bindex.gif" WIDTH=56 HEIGHT=21 ALT="Index page" BORDER=O></A><A HREF="II.html"><IMG SRC="images/bnext.gif" WIDTH=20 HEIGHT=21 ALT="Next file" BORDER=O></A>
 
 <!-- Google Analytics tracking code -->
 <script src="http://www.google-analytics.com/urchin.js" type="text/javascript">

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/1.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/1.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/1.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/1.html Mon Oct 15 13:36:02 2007
@@ -30,7 +30,6 @@
 <UL><LI><A HREF="1-2.html">1.2 Product Overview</A></LI></UL>
 <UL><UL><LI><A HREF="1-2.html#121">1.2.1 Components</A></LI></UL></UL>
 <UL><UL><LI><A HREF="1-2.html#122">1.2.2 STL Not Object-Oriented</A></LI></UL></UL>
-<UL><UL><LI><A HREF="1-2.html#123">1.2.3 Relationship to the Essential Tools Module</A></LI></UL></UL>
 <UL><LI><A HREF="1-3.html">1.3 Usage Notes</A></LI></UL>
 <UL><UL><LI><A HREF="1-3.html#131">1.3.1 Compatibility Issues</A></LI></UL></UL>
 <UL><UL><LI><A HREF="1-3.html#132">1.3.2 The std Namespace</A></LI></UL></UL>
@@ -41,10 +40,6 @@
 <UL><UL><LI><A HREF="1-5.html#152">1.5.2 Conventions</A></LI></UL></UL>
 <UL><UL><LI><A HREF="1-5.html#153">1.5.3 Organization</A></LI></UL></UL>
 <UL><UL><LI><A HREF="1-5.html#154">1.5.4 Reading Suggestion</A></LI></UL></UL>
-<UL><LI><A HREF="1-6.html">1.6 Consulting Services and Training</A></LI></UL>
-<UL><LI><A HREF="1-7.html">1.7 Technical Support</A></LI></UL>
-<UL><UL><LI><A HREF="1-7.html#171">1.7.1 To Obtain Technical Support</A></LI></UL></UL>
-<UL><UL><LI><A HREF="1-7.html#172">1.7.2 How to Contact Technical Support</A></LI></UL></UL>
 
 </UL>
 

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/16-1.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/16-1.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/16-1.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/16-1.html Mon Oct 15 13:36:02 2007
@@ -31,7 +31,7 @@
 <A NAME="idx393"><!></A>
 <P>The clearest example of this synthesis is the ability to extend the C++ Standard Library with user-defined containers and algorithms. This extension is possible because the definition of data structures has been separated from the definition of generic operations on those structures (<A HREF="1-2.html#122">Section&nbsp;1.2.2</A>). The library defines very specific parameters for these two broad groups, giving users some confidence that containers and algorithms from different sources will work together as long as they all meet the specifications of the standard. At the same time, containers encapsulate data and a limited range of operations on that data in classic OOP fashion.</P>
 <A NAME="idx394"><!></A>
-<P>Each standard container is categorized as one of two types: a <I>sequence</I> or an <I>associative container</I>. A user-defined container need not fit into either of these two groups since the standard also defines rudimentary requirements for a container, but the categorization can be very useful for determining which algorithms will work with a particular container and how efficiently those algorithms will work. In determining the category of a container, the most important characteristics are the <I>iterator category</I> and <I>element ordering</I>. (See the chapter on each container type, and the listing for each container and iterator in the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A>.)</P>
+<P>Each standard container is categorized as one of two types: a <I>sequence</I> or an <I>associative container</I>. A user-defined container need not fit into either of these two groups since the standard also defines rudimentary requirements for a container, but the categorization can be very useful for determining which algorithms will work with a particular container and how efficiently those algorithms will work. In determining the category of a container, the most important characteristics are the <I>iterator category</I> and <I>element ordering</I>. (See the chapter on each container type, and the listing for each container and iterator in the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A>.)</P>
 <A NAME="idx395"><!></A>
 <P>C++ Standard Library algorithms can be grouped into categories using a number of different criteria. The most important of these are: </P>
 <UL>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/16-3.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/16-3.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/16-3.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/16-3.html Mon Oct 15 13:36:02 2007
@@ -104,7 +104,7 @@
     iterator end() { return current_end; } 
   };
 </PRE></UL>
-<P>Given this class interface, here's a definition of a possible constructor that uses the allocator. The numbered comments following this code briefly describe the allocator's role. For a more thorough treatment of allocators, see <A HREF="15.html">Chapter&nbsp;15</A> and the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A> entry for allocators.</P>
+<P>Given this class interface, here's a definition of a possible constructor that uses the allocator. The numbered comments following this code briefly describe the allocator's role. For a more thorough treatment of allocators, see <A HREF="15.html">Chapter&nbsp;15</A> and the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A> entry for allocators.</P>
 
 <UL><PRE>
   template &lt;class T, class Allocator&gt;
@@ -141,7 +141,7 @@
 </TABLE>
 <A NAME="1633"><H3>16.3.3 Iterator Requirements</H3></A>
 <A NAME="idx407"><!></A>
-<P>Every container must define an iterator type. Iterators allow algorithms to iterate over the container's contents. Although iterators can range from simple to very complex, it is not the complexity but the<I> iterator category</I> that most affects an algorithm. The iterator category describes capabilities of the iterator, such as which direction it can traverse. <A HREF="16-4.html">Section&nbsp;16.4</A> and the iterator entries in the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A> provide additional information about iterator categories.</P>
+<P>Every container must define an iterator type. Iterators allow algorithms to iterate over the container's contents. Although iterators can range from simple to very complex, it is not the complexity but the<I> iterator category</I> that most affects an algorithm. The iterator category describes capabilities of the iterator, such as which direction it can traverse. <A HREF="16-4.html">Section&nbsp;16.4</A> and the iterator entries in the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A> provide additional information about iterator categories.</P>
 <P>The example in <A HREF="16-3.html#1632">Section&nbsp;16.3.2</A> shows the implementation of a container that uses a simple pointer. A simple pointer is actually an example of the most powerful type of iterator: the <I>random access iterator</I>. If an iterator supports random access, we can add to or subtract from it as easily as we can increment it.</P>
 <P>Some iterators have much less capability. For example, consider an iterator attached to a singly-linked <I>list</I>. Since each node in the <B><I><A HREF="../stdlibref/list.html">list</A></I></B> has links leading forward only, a naive iterator can advance through the container in only one direction. An iterator with this limitation falls into the category of forward iterator. </P>
 <P>Certain member functions such as <SAMP>begin()</SAMP> and <SAMP>end()</SAMP> produce iterators for a container. A container's description should always describe the category of iterator that its member functions produce. That way, a user of the container can see immediately which algorithms can operate successfully on the container.</P>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/17-2.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/17-2.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/17-2.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/17-2.html Mon Oct 15 13:36:02 2007
@@ -63,7 +63,7 @@
 <A NAME="idx418"><!></A>
 <P>The C++ Standard Library uses this technique to give the <B><I><A HREF="../stdlibref/basic-string.html">string</A></I></B> class maximum flexibility and efficiency across a wide range of types. The <B><I><A HREF="../stdlibref/char-traits.html">char_traits</A></I></B> traits class provides elementary operations on character arrays. In the simplest case, this means providing <B><I>string</I></B> a <SAMP>wstring</SAMP> with access to the C library functions for narrow and wide characters, for example <SAMP>strcpy</SAMP> and <SAMP>wcstrcpy</SAMP>.</P>
 <A NAME="idx419"><!></A>
-<P>See the <B><I><A HREF="../stdlibref/char-traits.html">char_traits</A></I></B> entry in the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A> for a complete description of the traits class.</P>
+<P>See the <B><I><A HREF="../stdlibref/char-traits.html">char_traits</A></I></B> entry in the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A> for a complete description of the traits class.</P>
 
 <BR>
 <HR>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/18-3.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/18-3.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/18-3.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/18-3.html Mon Oct 15 13:36:02 2007
@@ -26,7 +26,7 @@
 <A HREF="18-2.html"><IMG SRC="images/bprev.gif" WIDTH=20 HEIGHT=21 ALT="Previous file" BORDER=O></A><A HREF="noframes.html"><IMG SRC="images/btop.gif" WIDTH=56 HEIGHT=21 ALT="Top of Document" BORDER=O></A><A HREF="booktoc.html"><IMG SRC="images/btoc.gif" WIDTH=56 HEIGHT=21 ALT="Contents" BORDER=O></A><A HREF="tindex.html"><IMG SRC="images/bindex.gif" WIDTH=56 HEIGHT=21 ALT="Index page" BORDER=O></A><A HREF="18-4.html"><IMG SRC="images/bnext.gif" WIDTH=25 HEIGHT=21 ALT="Next file" BORDER=O></A><DIV CLASS="DOCUMENTNAME"><B>Apache C++ Standard Library User's Guide</B></DIV>
 <H2>18.3 Using Exceptions</H2>
 <A NAME="idx427"><!></A>
-<P>All exceptions thrown explicitly by any element of the C++ Standard Library are guaranteed to be part of the library's exception hierarchy. Please review the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A> entries for these classes to determine which functions throw which exceptions. You can then choose to catch particular exceptions, or catch any that might be thrown by specifying the base class exception. </P>
+<P>All exceptions thrown explicitly by any element of the Apache C++ Standard Library are guaranteed to be part of the library's exception hierarchy. Please review the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A> entries for these classes to determine which functions throw which exceptions. You can then choose to catch particular exceptions, or catch any that might be thrown by specifying the base class exception. </P>
 <P>For instance, if you are going to call the <SAMP>insert</SAMP> function on <B><I><A HREF="../stdlibref/basic-string.html">string</A></I></B> with a position value that could at some point be invalid, you should use code like this:</P>
 
 <UL><PRE>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/22-4.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/22-4.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/22-4.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/22-4.html Mon Oct 15 13:36:02 2007
@@ -53,7 +53,7 @@
 <A NAME="2242-2"><H4>22.4.2.2 The gslice Operation</H4></A>
 <A NAME="idx465"><!></A>
 <P>The <SAMP>gslice</SAMP> operation differs from the <SAMP>slice</SAMP> in that it defines a set of strides and an associated set of lengths. This set of lengths and strides allows a program to treat a single-dimensional <B><I><A HREF="../stdlibref/valarray.html">valarray</A></I></B> as a multidimensional array and to pull multi-dimensional slices from that array. Note that the <SAMP>gslice</SAMP> subset operator takes a <SAMP>gslice</SAMP> argument and returns a <B><I><A HREF="../stdlibref/gslice-array.html">gslice_array</A></I></B> in the same manner that the <SAMP>slice</SAMP> operation takes a <B><I><A HREF="../stdlibref/slice.html">slice</A></I></B> and returns a <B><I><A HREF="../stdlibref/slice-array.html">slice_array</A></I></B>.</P>
-<P>Here is a simple example that uses <B><I><A HREF="../stdlibref/gslice.html">gslice</A></I></B>s to represent a three-dimensional array. In this example, the first three numbers form the top row of a two-dimensional array whose center and bottom rows are completed with the next six numbers. The next nine numbers represent the second or <I>middle</I> two-dimensional array, and the last nine the <I>back</I> two-dimensional array. Taken together they form a three- dimensional <I>cube</I>. See the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A> for an extended version of this example that uses additional <B><I>gslice</I></B>s to pull <B><I><A HREF="../stdlibref/slice.html">slice</A></I></B>s along several different axes of the three-dimensional cube defined by this first slice.</P>
+<P>Here is a simple example that uses <B><I><A HREF="../stdlibref/gslice.html">gslice</A></I></B>s to represent a three-dimensional array. In this example, the first three numbers form the top row of a two-dimensional array whose center and bottom rows are completed with the next six numbers. The next nine numbers represent the second or <I>middle</I> two-dimensional array, and the last nine the <I>back</I> two-dimensional array. Taken together they form a three- dimensional <I>cube</I>. See the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A> for an extended version of this example that uses additional <B><I>gslice</I></B>s to pull <B><I><A HREF="../stdlibref/slice.html">slice</A></I></B>s along several different axes of the three-dimensional cube defined by this first slice.</P>
 
 <UL><PRE>
 using std::gslice;

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/22-7.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/22-7.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/22-7.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/22-7.html Mon Oct 15 13:36:02 2007
@@ -27,7 +27,7 @@
 <H2>22.7 Non-Member Functions</H2>
 <A NAME="2271"><H3>22.7.1 Binary Operators</H3></A>
 <A NAME="idx472"><!></A>
-<P>Class <B><I><A HREF="../stdlibref/valarray.html">valarray</A></I></B> provides a large block of binary operators that allow a program to apply these operators to two <B><I>valarray</I></B>s or to a <B><I>valarray</I></B> and a <SAMP>T</SAMP> value, where the <SAMP>T</SAMP> can occur on the left- or right-hand side of the expression. As you'd expect, these operators do not modify either of their arguments, but instead return a new <B><I>valarray</I></B> containing the result of the operation. Each version that takes two <B><I>valarray</I></B> arguments returns the result of applying the operation to the corresponding elements of the arrays. The versions with a <SAMP>T&amp;</SAMP> argument return a <B><I>valarray</I></B> whose elements result from applying the operation to each element in the <B><I>valarray</I></B> argument along with the <SAMP>T&amp;</SAMP> argument. See the <B><I>valarray</I></B> entry in the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Mo
 dule Reference Guide</I></A> for a complete list of binary operators.</P>
+<P>Class <B><I><A HREF="../stdlibref/valarray.html">valarray</A></I></B> provides a large block of binary operators that allow a program to apply these operators to two <B><I>valarray</I></B>s or to a <B><I>valarray</I></B> and a <SAMP>T</SAMP> value, where the <SAMP>T</SAMP> can occur on the left- or right-hand side of the expression. As you'd expect, these operators do not modify either of their arguments, but instead return a new <B><I>valarray</I></B> containing the result of the operation. Each version that takes two <B><I>valarray</I></B> arguments returns the result of applying the operation to the corresponding elements of the arrays. The versions with a <SAMP>T&amp;</SAMP> argument return a <B><I>valarray</I></B> whose elements result from applying the operation to each element in the <B><I>valarray</I></B> argument along with the <SAMP>T&amp;</SAMP> argument. See the <B><I>valarray</I></B> entry in the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Lib
 rary Reference Guide</I></A> for a complete list of binary operators.</P>
 <P>Arithmetic and bitwise operators return a <B><I><A HREF="../stdlibref/valarray.html">valarray</A></I></B> of <SAMP>T</SAMP>. Logical operators return a <B><I>valarray&lt;bool&gt;</I></B>, where each element represents the comparison of corresponding elements in two <B><I>valarray</I></B>s or the comparison of each element in an array with a particular value. For example:</P>
 
 <UL><PRE>
@@ -43,7 +43,7 @@
 </PRE></UL>
 <A NAME="2272"><H3>22.7.2 Transcendental Functions</H3></A>
 <A NAME="idx473"><!></A>
-<P>Class <B><I><A HREF="../stdlibref/valarray.html">valarray</A></I></B> also provides 20 transcendental functions, four of which are overloads. Each function returns a new <B><I>valarray</I></B> that contains elements resulting from the application of the transcendental function to each element in the <B><I>valarray</I></B> passed as an argument. See the <B><I>valarray</I></B> entry in the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A> for a complete list of transcendental functions. </P>
+<P>Class <B><I><A HREF="../stdlibref/valarray.html">valarray</A></I></B> also provides 20 transcendental functions, four of which are overloads. Each function returns a new <B><I>valarray</I></B> that contains elements resulting from the application of the transcendental function to each element in the <B><I>valarray</I></B> passed as an argument. See the <B><I>valarray</I></B> entry in the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A> for a complete list of transcendental functions. </P>
 <P>The following example squares each of the elements of an array:</P>
 
 <UL><PRE>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/24-2.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/24-2.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/24-2.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/24-2.html Mon Oct 15 13:36:02 2007
@@ -41,7 +41,7 @@
 <A NAME="idx516"><!></A>
 <P>The C locale is composed of six categories of locale-dependent information: <SAMP>LC_NUMERIC</SAMP> (rules and symbols for numbers), <SAMP>LC_TIME</SAMP> (values for date and time information), <SAMP>LC_MONETARY</SAMP> (rules and symbols for monetary information), <SAMP>LC_CTYPE</SAMP> (character classification and conversion), <SAMP>LC_COLLATE</SAMP> (collation sequence), and <SAMP>LC_MESSAGES</SAMP> (formats and values of messages). </P>
 <A NAME="idx517"><!></A>
-<P>Similarly, there are six categories of standard facet classes. A detailed description of these facets is contained in the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A>, but a brief overview is given below. Note that an abbreviation like <B><I><A HREF="../stdlibref/num-get.html">num_get&lt;&gt;</A></I></B> means that <B><I>num_get</I></B> is a class template taking two template arguments, a character type, and an input iterator type. The categories of the standard facets are:</P>
+<P>Similarly, there are six categories of standard facet classes. A detailed description of these facets is contained in the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A>, but a brief overview is given below. Note that an abbreviation like <B><I><A HREF="../stdlibref/num-get.html">num_get&lt;&gt;</A></I></B> means that <B><I>num_get</I></B> is a class template taking two template arguments, a character type, and an input iterator type. The categories of the standard facets are:</P>
 <UL>
 <A NAME="idx518"><!></A>
 <LI><P CLASS="LIST"><B>Numeric. </B>The facet classes <B><I><A HREF="../stdlibref/num-get.html">num_get&lt;&gt;</A></I></B> and <B><I><A HREF="../stdlibref/num-put.html">num_put&lt;&gt;</A></I></B> handle numeric formatting and parsing. The facet classes provide <SAMP>get()</SAMP> and <SAMP>put()</SAMP> member functions for values of type <SAMP>long</SAMP>, <SAMP>double</SAMP>, etc.</P></LI>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/24-4.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/24-4.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/24-4.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/24-4.html Mon Oct 15 13:36:02 2007
@@ -42,7 +42,7 @@
 <TR VALIGN="top"><TD><SAMP>//1</SAMP></TD><TD>You can create a locale object from a C locale's external representation. The constructor <SAMP>std::locale::locale(const char* std_name)</SAMP> takes the name of a C locale. This locale name is like the one you would use for a call to the C library function <SAMP>setlocale()</SAMP>.
 <TR VALIGN="top"><TD><SAMP>//2</SAMP></TD><TD>You can also use a predefined locale object, returned by <SAMP>std::locale::classic()</SAMP>, which represents the US English ASCII environment.
 </TABLE>
-<P>For a comprehensive description of the constructors described above, see the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A>.</P>
+<P>For a comprehensive description of the constructors described above, see the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A>.</P>
 <A NAME="idx551"><!></A>
 <P>It's important to understand that locales are immutable objects: once a locale object is created, it cannot be modified. This makes locales reliable and easy to use. As a programmer, you know that whenever you use pointers or references to elements held in a container, you have to worry about the validity of the pointers and references. If the container changes, pointers and references to its elements might not be valid any longer.</P>
 <P>A locale object is a container, too. However, it is an immutable container; that is, it does not change. Therefore, you can take references to a locale's facet objects and pass the references around without worrying about their validity, as long as the locale object or any copy of it remains in existence. The locale object is never modified; no facets can be silently replaced.</P>
@@ -65,7 +65,7 @@
 std::locale loc(std::locale::classic(),
                 std::locale("De_DE"), LC_NUMERIC);
 </PRE></UL>
-<P>For a comprehensive description of the constructors described above, see the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A>.</P>
+<P>For a comprehensive description of the constructors described above, see the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A>.</P>
 <A NAME="idx554"><!></A>
 <P>Copying a locale object is a cheap operation. You should have no hesitation about passing locale objects around by value. You may copy locale objects for composing new locale objects; you may pass copies of locale objects as arguments to functions, etc. </P>
 <A NAME="idx555"><!></A>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/25-5.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/25-5.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/25-5.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/25-5.html Mon Oct 15 13:36:02 2007
@@ -98,7 +98,7 @@
 <TR VALIGN="top"><TD><SAMP>//2</SAMP></TD><TD>The new facet is derived from the <SAMP>std::numpunct_byname&lt;charT&gt;</SAMP> facet.
 <BR><BR>The byname facets read the respective locale information from the external representation of a C locale. The name provided to construct a byname<I> </I>facet is the name of a locale, as you would use it in a call to <SAMP>setlocale()</SAMP>.
 <TR VALIGN="top"><TD><SAMP>//3</SAMP></TD><TD>A constructor is provided that takes a locale name and the new values we want to display for the alpha versions of <SAMP>true</SAMP> and <SAMP>false</SAMP>. The fourth parameter, <SAMP>refs</SAMP>, controls the facet's lifetime, as described in an earlier section.
-<TR VALIGN="top"><TD><SAMP>//4</SAMP></TD><TD>The virtual member functions <SAMP>do_truename()</SAMP> and <SAMP>do_falsename()</SAMP> are reimplemented. They are called by the public member functions <SAMP>truename()</SAMP> and <SAMP>falsename()</SAMP>. See the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A> for further details.
+<TR VALIGN="top"><TD><SAMP>//4</SAMP></TD><TD>The virtual member functions <SAMP>do_truename()</SAMP> and <SAMP>do_falsename()</SAMP> are reimplemented. They are called by the public member functions <SAMP>truename()</SAMP> and <SAMP>falsename()</SAMP>. See the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A> for further details.
 </TABLE>
 <P>Now let's create a German locale in which the <SAMP>std::numpunct&lt;char&gt;</SAMP> facet has been replaced by an object of our new derived facet type, as shown in <A HREF="25-5.html#Figure&nbsp;11">Figure&nbsp;11</A>:</P>
 <A NAME="idx580"><!></A>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/27-3.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/27-3.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/27-3.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/27-3.html Mon Oct 15 13:36:02 2007
@@ -30,7 +30,7 @@
 <UL>
 <A NAME="idx636"><!></A>
 <LI><P CLASS="LIST"><B>File I/O. </B>Iostreams can still be used for input and output to files, although file I/O has lost some of it former importance. In the past, alpha-numeric user interfaces were often built using file input/output to the standard input and output channels. Today almost all applications have graphical user interfaces.</P></LI>
-<P CLASS="LIST">Nevertheless, iostreams are still useful for input and output to files other than the standard input and output channels, and to all other kinds of external media that fit into the file abstraction. For example, SourcePro Net, Rogue Wave Software's product for network communications programming, uses iostreams for input and output to communication streams such as sockets and pipes.</P>
+<P CLASS="LIST">Nevertheless, iostreams are still useful for input and output to files other than the standard input and output channels, and to all other kinds of external media that fit into the file abstraction. For example, you could use iostreams for input and output to communication streams such as sockets and pipes.</P>
 <A NAME="idx637"><!></A>
 <LI><P CLASS="LIST"><B>In-Memory I/O.</B> Iostreams can perform in-memory formatting and parsing. Even with a graphical user interface, you must format the text you want to display. The standard iostreams offer internationalized in-memory I/O, which is a great help for text processing tasks like formatting. The formatting of numeric values, for example, depends on cultural conventions. The formatting layer uses a locale's numeric facets to adapt its formatting and parsing to cultural conventions.</P></LI>
 <A NAME="idx638"><!></A>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/27-4.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/27-4.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/27-4.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/27-4.html Mon Oct 15 13:36:02 2007
@@ -40,7 +40,7 @@
 
 <P><IMG SRC="images/stdlibug-IOStreams7.gif" WIDTH=592 HEIGHT=499></P>
 <A NAME="idx645"><!></A>
-<P>You may notice that the classes <B><I><A HREF="../stdlibref/strstream.html">strstream</A></I></B>, <B><I><A HREF="../stdlibref/istrstream.html">istrstream</A></I></B>, and <B><I><A HREF="../stdlibref/ostrstream.html">ostrstream</A></I></B> are not included in this diagram, even though we describe them in the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A>. Sometimes called <I>deprecated features</I> in the standard, these classes are provided solely for the sake of compatibility with the traditional iostreams, and will not be supported in future versions of the standard iostreams. </P>
+<P>You may notice that the classes <B><I><A HREF="../stdlibref/strstream.html">strstream</A></I></B>, <B><I><A HREF="../stdlibref/istrstream.html">istrstream</A></I></B>, and <B><I><A HREF="../stdlibref/ostrstream.html">ostrstream</A></I></B> are not included in this diagram, even though we describe them in the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A>. Sometimes called <I>deprecated features</I> in the standard, these classes are provided solely for the sake of compatibility with the traditional iostreams, and will not be supported in future versions of the standard iostreams. </P>
 <P>In the next sections, we discuss in more detail the components and characteristics of the components that are included in the class hierarchy given in <A HREF="27-4.html#Figure&nbsp;23">Figure&nbsp;23</A>.</P>
 <A NAME="idx646"><!></A>
 <A NAME="2741-1"><H4>27.4.1.1 Iostreams Base Class ios_base</H4></A>
@@ -83,7 +83,7 @@
 <A NAME="idx656"><!></A>
 <LI><P CLASS="LIST"><B>The equality of two characters</B>. For an exotic user-defined character type, the equality of two characters might mean something different from just bit-wise equality. Here you can define it.</P></LI>
 </UL>
-<P>A complete list of character traits is given in the <I>C++ Standard Library Module Reference Guide</I> entry for <SAMP>char_traits</SAMP>.</P>
+<P>A complete list of character traits is given in the <I>Apache C++ Standard Library Reference Guide</I> entry for <SAMP>char_traits</SAMP>.</P>
 <P>There are specializations defined for type <SAMP>char</SAMP> and <SAMP>wchar_t</SAMP>. In general, this class template is not meant to be explicitly instantiated for a user-defined character type. You should always define class template specializations.</P>
 <P>Fortunately, the C++ Standard Library is designed to make the most common cases the easiest. The traits template parameter has a sensible default value, so usually you need not bother with character traits at all.</P>
 <A NAME="idx657"><!></A>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/28-3.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/28-3.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/28-3.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/28-3.html Mon Oct 15 13:36:02 2007
@@ -63,7 +63,7 @@
 <P>Typically, these would have just two or three different values. These parameters are represented by one or more bits in a data member of type <SAMP>std::iosbase::fmtflags</SAMP> in class <B><I><A HREF="../stdlibref/ios-base.html">ios_base</A></I></B>. These are usually called <I>format flags</I>. You can set format flags using the <SAMP>setf()</SAMP> function in class <B><I>ios_base</I></B>, clear them using <SAMP>unsetf()</SAMP>, and retrieve them through the <SAMP>flags()</SAMP> function.</P>
 <A NAME="idx706"><!></A>
 <P>Some format flags are grouped because they are mutually exclusive; for example, output within an output field can be adjusted to the left or to the right, or to an internally specified adjustment. One and only one of the corresponding three format flags, <SAMP>left</SAMP>, <SAMP>right</SAMP>, or <SAMP>internal</SAMP>, can be set. (Iostreams does not prevent you from setting other invalid combinations of these flags, however.) If you want to set one of these bits to <SAMP>1</SAMP>, you need to set the other two to <SAMP>0</SAMP>. To make this easier, there are <I>bit groups</I> whose main function is to reset all bits in one group. The bit group for adjustment is <SAMP>adjustfield</SAMP>, defined as <SAMP>left | right | internal</SAMP>. </P>
-<P><A HREF="28-3.html#Table&nbsp;28">Table&nbsp;28</A> gives an overview of all format flags and their effects on input and output operators. (For details on how the format flags affect input and output operations, see the <I>C++ Standard Library Module Reference Guide</I> entry for <B><I><A HREF="../stdlibref/ios-base.html">ios_base</A></I></B>.) The first column below<I>, format flag</I>, lists the flag names; for example, <SAMP>showpos</SAMP> stands for <SAMP>std::ios_base::showpos</SAMP>. The<I> group</I> column lists the name of the group for flags that are mutually exclusive. The third column gives a brief description of the effect of setting the flag. The <I>stdio</I> column refers to format characters used by the C functions <SAMP>scanf()</SAMP> or <SAMP>printf()</SAMP> that have the same or similar effect. The last column, <I>default</I>, lists the setting that is used if you do not explicitly set the flag.</P>
+<P><A HREF="28-3.html#Table&nbsp;28">Table&nbsp;28</A> gives an overview of all format flags and their effects on input and output operators. (For details on how the format flags affect input and output operations, see the <I>Apache C++ Standard Library Reference Guide</I> entry for <B><I><A HREF="../stdlibref/ios-base.html">ios_base</A></I></B>.) The first column below<I>, format flag</I>, lists the flag names; for example, <SAMP>showpos</SAMP> stands for <SAMP>std::ios_base::showpos</SAMP>. The<I> group</I> column lists the name of the group for flags that are mutually exclusive. The third column gives a brief description of the effect of setting the flag. The <I>stdio</I> column refers to format characters used by the C functions <SAMP>scanf()</SAMP> or <SAMP>printf()</SAMP> that have the same or similar effect. The last column, <I>default</I>, lists the setting that is used if you do not explicitly set the flag.</P>
 <A NAME="idx707"><!></A>
 <H4><A NAME="Table&nbsp;28">Table&nbsp;28: Flags and their effects on operators&nbsp;</A></H4>
 <TABLE BORDER="1" CELLPADDING="3" CELLSPACING="3">

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/30-2.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/30-2.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/30-2.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/30-2.html Mon Oct 15 13:36:02 2007
@@ -51,7 +51,7 @@
 <TR VALIGN="top"><TD><SAMP>//3</SAMP></TD><TD>Here the file is both opened and connected to the stream.
 </TABLE>
 <BLOCKQUOTE><HR><B>
-NOTE -- The traditional iostreams supported a constructor, taking a file descriptor, that allowed connection of a file stream to an already open file. This is not available in the standard iostreams. However, this implementation of the standard iostreams provides a corresponding extension. See Appendix B of the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A> for more information.
+NOTE -- The traditional iostreams supported a constructor, taking a file descriptor, that allowed connection of a file stream to an already open file. This is not available in the standard iostreams. However, this implementation of the standard iostreams provides a corresponding extension. See Appendix B of the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A> for more information.
 </B><HR></BLOCKQUOTE>
 <A NAME="3022"><H3>30.2.2 Checking a File Stream's Status</H3></A>
 <A NAME="idx745"><!></A>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/32-5.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/32-5.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/32-5.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/32-5.html Mon Oct 15 13:36:02 2007
@@ -33,7 +33,7 @@
 <P>However, the more general question here is: What are inserters and extractors supposed to do? Some recommendations follow.</P>
 <P><B><I>Regarding </I></B><B>format flags</B><B><I>, inserters and extractors should:</I></B></P>
 <UL>
-<LI><P CLASS="LIST">Create a sentry object right at the beginning of every inserter and extractor. In its constructor and destructor, the sentry performs certain standard tasks, like skipping white characters, flushing tied streams, etc. See the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A> for a detailed explanation.</P></LI>
+<LI><P CLASS="LIST">Create a sentry object right at the beginning of every inserter and extractor. In its constructor and destructor, the sentry performs certain standard tasks, like skipping white characters, flushing tied streams, etc. See the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A> for a detailed explanation.</P></LI>
 <LI><P CLASS="LIST">Reset the width after each usage.</P></LI>
 </UL>
 <P><B><I>Regarding </I></B><B>state bits</B><B><I>, inserters and extractors should:</I></B></P>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/33-3.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/33-3.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/33-3.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/33-3.html Mon Oct 15 13:36:02 2007
@@ -98,7 +98,7 @@
    Arg2   arg2_;
 };
 </PRE></UL>
-<P>Note that this is only a suggested manipulator, however. In principle, you can define the manipulator type in any way that makes the associated side effect function and its arguments available for a call from inside the respective shift operators for the manipulator type. We show other examples of such manipulator types later in this chapter; for instance, a manipulator type called smanip mentioned by the C++ standard. It is an implementation-defined function type returned by the standard manipulators. See the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A> for details.</P>
+<P>Note that this is only a suggested manipulator, however. In principle, you can define the manipulator type in any way that makes the associated side effect function and its arguments available for a call from inside the respective shift operators for the manipulator type. We show other examples of such manipulator types later in this chapter; for instance, a manipulator type called smanip mentioned by the C++ standard. It is an implementation-defined function type returned by the standard manipulators. See the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A> for details.</P>
 <A NAME="idx816"><!></A>
 <P>Returning now to the example above, the manipulator object provided as an argument to the overloaded shift operator is obtained by <SAMP>Manip(x)</SAMP>, which has three possible solutions:</P>
 <OL>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/36-3.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/36-3.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/36-3.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/36-3.html Mon Oct 15 13:36:02 2007
@@ -66,7 +66,7 @@
 <TABLE CELLPADDING="3">
 
 <TR VALIGN="top"><TD><SAMP>//1</SAMP></TD><TD>The manipulator class owns the index of the element in the iostream storage where we want to store the format string. It is initialized in <SAMP>//4</SAMP> by a call to <SAMP>xalloc()</SAMP>.
-<TR VALIGN="top"><TD><SAMP>//2</SAMP></TD><TD>The manipulator accesses the array <SAMP>pword()</SAMP> using the index <SAMP>datfmtIdx</SAMP>, and stores the pointer to the date format string. [For brevity, error handling is omitted in the example. If allocation fails, then <SAMP>std::ios_base::badbit</SAMP> is set.] Note that the reference returned by <SAMP>pword()</SAMP> is only used for <I>storing</I> the pointer to the date format string. Generally, you should never store a reference returned by <SAMP>iword()</SAMP> or <SAMP>pword()</SAMP> in order to access the stored data through this reference later on. This is because these references can become invalid once the array is reallocated or copied. (See the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A> for more details.)
+<TR VALIGN="top"><TD><SAMP>//2</SAMP></TD><TD>The manipulator accesses the array <SAMP>pword()</SAMP> using the index <SAMP>datfmtIdx</SAMP>, and stores the pointer to the date format string. [For brevity, error handling is omitted in the example. If allocation fails, then <SAMP>std::ios_base::badbit</SAMP> is set.] Note that the reference returned by <SAMP>pword()</SAMP> is only used for <I>storing</I> the pointer to the date format string. Generally, you should never store a reference returned by <SAMP>iword()</SAMP> or <SAMP>pword()</SAMP> in order to access the stored data through this reference later on. This is because these references can become invalid once the array is reallocated or copied. (See the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A> for more details.)
 <TR VALIGN="top"><TD><SAMP>//3</SAMP></TD><TD>The inserter for <SAMP>date</SAMP> objects needs to access the index into the array of pointers, so that it can read the format string and use it. Therefore, the inserter must be declared as a friend. In principle, the extractor must be a friend, too; however, the standard C++ locale falls short of supporting the use of format strings like the ones used by the standard C function <SAMP>strptime()</SAMP>. Hence, the implementation of a date extractor that supports date format strings would be a lot more complicated than the implementation for the inserter, which can use the stream's locale. We have omitted the extractor for the sake of brevity.
 <TR VALIGN="top"><TD><SAMP>//4</SAMP></TD><TD>Initializes the index of elements in istream storage where the format string is kept.
 </TABLE>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/39-1.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/39-1.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/39-1.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/39-1.html Mon Oct 15 13:36:02 2007
@@ -57,7 +57,7 @@
 <A NAME="idx931"><!></A>
 <A NAME="3912"><H3>39.1.2 The streambuf Interface</H3></A>
 <A NAME="idx932"><!></A>
-<P><B><I><A HREF="../stdlibref/basic-streambuf.html">basic_streambuf</A></I></B> defines a public interface for reading, writing, seeking, querying, and localization. Most of the public functions that define this interface actually delegate to protected virtual functions so that specific behavior is implemented by derived classes. The <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A> contains detailed descriptions of all of these functions. Meanwhile, the public interface, and the way in which functions delegate to virtual functions, is described below:</P>
+<P><B><I><A HREF="../stdlibref/basic-streambuf.html">basic_streambuf</A></I></B> defines a public interface for reading, writing, seeking, querying, and localization. Most of the public functions that define this interface actually delegate to protected virtual functions so that specific behavior is implemented by derived classes. The <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A> contains detailed descriptions of all of these functions. Meanwhile, the public interface, and the way in which functions delegate to virtual functions, is described below:</P>
 <A NAME="idx933"><!></A>
 <P><B><I>For reading:</I></B></P>
 <P>The <SAMP>in_avail()</SAMP> member function returns the number of characters currently in the buffer that are available for reading, or an estimate of the number of characters available in the underlying source if the buffer is currently empty. If an estimate cannot be obtained, as may be the case with the standard iostream object <SAMP>std::cin</SAMP>, then this function returns<SAMP> -1</SAMP>.</P>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/40-5.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/40-5.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/40-5.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/40-5.html Mon Oct 15 13:36:02 2007
@@ -98,7 +98,7 @@
  }
 };
 </PRE></UL>
-<P>In this case, the member function <SAMP>do_encoding()</SAMP> has to return <SAMP>-1</SAMP>, which identifies the code conversion as state-dependent. Again, the member functions <SAMP>in()</SAMP> and <SAMP>out()</SAMP> must conform to the error indication policy explained under class <B><I><A HREF="../stdlibref/codecvt.html">codecvt</A></I></B> in the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A>.</P>
+<P>In this case, the member function <SAMP>do_encoding()</SAMP> has to return <SAMP>-1</SAMP>, which identifies the code conversion as state-dependent. Again, the member functions <SAMP>in()</SAMP> and <SAMP>out()</SAMP> must conform to the error indication policy explained under class <B><I><A HREF="../stdlibref/codecvt.html">codecvt</A></I></B> in the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A>.</P>
 <P>The distinguishing characteristic of a state-independent conversion is that the conversion state argument to <SAMP>in()</SAMP> and <SAMP>out()</SAMP> is used for communication between the file stream buffer and the code conversion facet. The file stream buffer is responsible for creating, maintaining, and deleting the conversion state. At the beginning, the file stream buffer creates a conversion state object that represents the initial conversion state and hands it over to the code conversion facet. The facet modifies it according to the conversion it performs. The file stream buffer receives it and stores it between two subsequent code conversions.</P>
 <A NAME="4054"><H3>40.5.4 Use the New Code Conversion Facet</H3></A>
 <A NAME="idx964"><!></A>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/41-2.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/41-2.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/41-2.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/41-2.html Mon Oct 15 13:36:02 2007
@@ -62,7 +62,7 @@
   static int_type eof();
 };
 </PRE></UL>
-<P>See the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A> section on <A HREF="../stdlibref/char-traits.html">char_traits</A> for a complete description of the member functions in a traits class.</P>
+<P>See the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A> section on <A HREF="../stdlibref/char-traits.html">char_traits</A> for a complete description of the member functions in a traits class.</P>
 <P>To create a new code conversion facet, you must inherit from the <SAMP>std::codecvt</SAMP> template and then override some or all the protected virtual functions. Iostreams calls the protected functions through the public interface defined for <SAMP>std::codecvt</SAMP>. You must also provide a constructor taking a single <SAMP>std::size_t</SAMP> argument, and initialize <SAMP>codecvt</SAMP> with that argument.</P>
 <A NAME="idx969"><!></A>
 <P>A code conversion facet for <SAMP>Echar</SAMP> has a declaration that looks like this:</P>
@@ -97,7 +97,7 @@
          virtual int do_max_length() const throw();
 };
 </PRE></UL>
-<P>See <A HREF="40.html">Chapter&nbsp;40</A> on defining a code conversion facet for more details. Also see the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A> section on <A HREF="../stdlibref/codecvt.html">codecvt</A> for a complete description of member functions.</P>
+<P>See <A HREF="40.html">Chapter&nbsp;40</A> on defining a code conversion facet for more details. Also see the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A> section on <A HREF="../stdlibref/codecvt.html">codecvt</A> for a complete description of member functions.</P>
 <P>To create a character classification facet, you must inherit from the <SAMP>std::ctype</SAMP> template and provide implementations for all protected virtual functions. You must also provide a constructor taking a single <SAMP>std::size_t</SAMP> argument, and initialize <SAMP>std::ctype</SAMP> with that argument.</P>
 <P>Note that the <SAMP>widen()</SAMP> functions define conversions from simple <SAMP>char</SAMP>s to the user-defined character type, and the narrow function provides conversions from the user-defined type to simple <SAMP>char</SAMP>s.</P>
 <A NAME="idx970"><!></A>

Modified: incubator/stdcxx/branches/4.2.0/doc/stdlibug/42-1.html
URL: http://svn.apache.org/viewvc/incubator/stdcxx/branches/4.2.0/doc/stdlibug/42-1.html?rev=584901&r1=584900&r2=584901&view=diff
==============================================================================
--- incubator/stdcxx/branches/4.2.0/doc/stdlibug/42-1.html (original)
+++ incubator/stdcxx/branches/4.2.0/doc/stdlibug/42-1.html Mon Oct 15 13:36:02 2007
@@ -31,7 +31,7 @@
 <LI><P CLASS="LIST">The formatting layer of iostreams uses <B><I><A HREF="../stdlibref/locale.html">locale</A></I></B> facilities for numeric formatting and character classification.</P></LI>
 <LI><P CLASS="LIST">The transport layer uses <B><I><A HREF="../stdlibref/locale.html">locale</A></I></B> facilities for code conversion.</P></LI>
 </UL>
-<P>In the standard iostream class templates, the formatting (stream) layer uses only the <B><I><A HREF="../stdlibref/ctype.html">ctype</A></I></B>, <B><I><A HREF="../stdlibref/num-put.html">num_put</A></I></B>, and <B><I><A HREF="../stdlibref/num-get.html">num_get</A></I></B> facets, while the transport (stream buffer) layer uses only the <B><I><A HREF="../stdlibref/codecvt.html">codecvt</A></I></B> facet. For more information on locales and facets, see <A HREF="24.html">Chapter&nbsp;24</A> and the sections of the <A HREF="../stdlibref/noframes.html"><I>C++ Standard Library Module Reference Guide</I></A> devoted to the <B><I><A HREF="../stdlibref/locale.html">locale</A></I></B> class and the various facets.</P>
+<P>In the standard iostream class templates, the formatting (stream) layer uses only the <B><I><A HREF="../stdlibref/ctype.html">ctype</A></I></B>, <B><I><A HREF="../stdlibref/num-put.html">num_put</A></I></B>, and <B><I><A HREF="../stdlibref/num-get.html">num_get</A></I></B> facets, while the transport (stream buffer) layer uses only the <B><I><A HREF="../stdlibref/codecvt.html">codecvt</A></I></B> facet. For more information on locales and facets, see <A HREF="24.html">Chapter&nbsp;24</A> and the sections of the <A HREF="../stdlibref/noframes.html"><I>Apache C++ Standard Library Reference Guide</I></A> devoted to the <B><I><A HREF="../stdlibref/locale.html">locale</A></I></B> class and the various facets.</P>
 <P>Each layer contains its own <B><I><A HREF="../stdlibref/locale.html">locale</A></I></B>, so the code conversion facility can be changed independent of numeric formatting. We simply change the <B><I>locale</I></B> associated with a stream buffer without altering the <B><I>locale</I></B> contained by the stream using that buffer.   On the other hand, changing a stream's <B><I>locale</I></B> also changes the <B><I>locale</I></B> contained by the associated stream buffer.</P>
 <P>The base class for all streams, <B><I><A HREF="../stdlibref/ios-base.html">ios_base</A></I></B>, contains a <B><I><A HREF="../stdlibref/locale.html">locale</A></I></B> object. This <B><I>locale</I></B> object can be accessed with the <SAMP>getloc()</SAMP> member function and replaced with the <SAMP>imbue()</SAMP> member function. Similarly, <B><I><A HREF="../stdlibref/basic-streambuf.html">basic_streambuf</A></I></B> also contains a <B><I>locale</I></B> object and it, too, defines <SAMP>getloc()</SAMP> and <SAMP>imbue()</SAMP> member functions  (the latter is <SAMP>protected</SAMP> and <SAMP>virtual</SAMP> and called from the publicly accessible <SAMP>pubimbue()</SAMP> member function).</P>
 



Mime
View raw message