This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [v3] documentation on cstdio and synchronization
Fixes the ones Nathan pointed out, plus one more I happened to spot.
("itererator"? Has Dubya been editing our headers?)
2001-07-09 Phil Edwards <pme@sources.redhat.com>
* docs/html/configopts.html: Fix thinko.
* docs/html/27_io/howto.html: Fix thinko and HTML markup.
* include/bits/stl_iterator.h: Fix typo.
Index: docs/html/configopts.html
===================================================================
RCS file: /cvs/gcc/gcc/libstdc++-v3/docs/html/configopts.html,v
retrieving revision 1.11
diff -u -3 -p -r1.11 configopts.html
--- configopts.html 2001/07/09 19:37:01 1.11
+++ configopts.html 2001/07/09 21:46:31
@@ -71,7 +71,7 @@ options</A></H1>
</P>
<DT><TT>--enable-sjlj-exceptions </TT>
- <DD><P>Forces old, short-jump/long-jump exception handling model. If
+ <DD><P>Forces old, set-jump/long-jump exception handling model. If
at all possible, the new, frame unwinding exception handling routines
should be used instead, as they significantly reduce both runtime
memory usage and executable size.
Index: docs/html/27_io/howto.html
===================================================================
RCS file: /cvs/gcc/gcc/libstdc++-v3/docs/html/27_io/howto.html,v
retrieving revision 1.6
diff -u -3 -p -r1.6 howto.html
--- howto.html 2001/07/09 19:37:01 1.6
+++ howto.html 2001/07/09 21:46:31
@@ -425,7 +425,7 @@
involve doing very little buffering for the standard streams, leaving
most of the buffering to the underlying C library. (This kind of
thing is <A HREF="../explanations.html#cstdio">tricky to get right</A>.)
- The upside is that correctness is insured. The downside is that
+ The upside is that correctness is ensured. The downside is that
writing through <TT>cout</TT> can quite easily lead to awful
performance when the C++ I/O library is layered on top of the C I/O
library (as it is for 3.0 by default). Some patches are in the
@@ -447,9 +447,10 @@
company will become fully buffered on their own.
</P>
<P>Note, by the way, that the synchronization requirement only applies to
- the standard streams (cin, cout, cerr, clog, and thier wide-character
- counterparts). File stream objects that you create yourself have no
- such requirement and are fully buffered.
+ the standard streams (<TT>cin</TT>, <TT>cout</TT>, <TT>cerr</TT>,
+ <TT>clog</TT>, and their wide-character counterparts). File stream
+ objects that you create yourself have no such requirement and are fully
+ buffered.
</P>
Index: include/bits/stl_iterator.h
===================================================================
RCS file: /cvs/gcc/gcc/libstdc++-v3/include/bits/stl_iterator.h,v
retrieving revision 1.11
diff -u -3 -p -r1.11 stl_iterator.h
--- stl_iterator.h 2001/06/27 17:09:52 1.11
+++ stl_iterator.h 2001/07/09 21:46:31
@@ -320,7 +320,7 @@ namespace std
}
// This iterator adapter is 'normal' in the sense that it does not
- // change the semantics of any of the operators of its itererator
+ // change the semantics of any of the operators of its iterator
// parameter. Its primary purpose is to convert an iterator that is
// not a class, e.g. a pointer, into an iterator that is a class.
// The _Container parameter exists solely so that different containers