From c5504edb751bff4f5b2a493921466d04857494f4 Mon Sep 17 00:00:00 2001
From: Joseph Myers
Here is a small link farm to threads (no pun) in the mail archives that discuss the threading problem. Each link is to the first - relevent message in the thread; from there you can use + relevant message in the thread; from there you can use "Thread Next" to move down the thread. This farm is in latest-to-oldest order.
This section will be updated as new and interesting issues come to light. diff --git a/libstdc++-v3/docs/html/17_intro/porting.html b/libstdc++-v3/docs/html/17_intro/porting.html index 291393c60a9..344fb4f31b3 100644 --- a/libstdc++-v3/docs/html/17_intro/porting.html +++ b/libstdc++-v3/docs/html/17_intro/porting.html @@ -140,7 +140,7 @@ Up:Top
The library requires that you provide three header files to implement
-character classification, analagous to that provided by the C libraries
+character classification, analogous to that provided by the C libraries
<ctype.h> header. You can model these on the files provided in
config/os/generic/bits. However, these files will almost
certainly need some modification.
@@ -149,7 +149,7 @@ certainly need some modification.
some very basic information about character classification. The libstdc++-v3
library assumes that your C library implements <ctype.h> by using
a table (indexed by character code) containing integers, where each of
-these integers is a bit-mask indicating whether the charcter is
+these integers is a bit-mask indicating whether the character is
upper-case, lower-case, alphabetic, etc. The bits/ctype_base.h
file gives the type of the integer, and the values of the various bit
masks. You will have to peer at your own <ctype.h> to figure out
@@ -273,7 +273,7 @@ contains a few more functions. On most systems, you can just copy
config/os/generic/ctype_inline.h and use it on your system.
In detail, the functions provided test characters for particular
-properties; they are analagous to the functions like isalpha and
+properties; they are analogous to the functions like isalpha and
islower provided by the C library.
The first function is implemented like this on IRIX:
diff --git a/libstdc++-v3/docs/html/17_intro/porting.texi b/libstdc++-v3/docs/html/17_intro/porting.texi
index 018cbdeb41f..d5d32b4a2f4 100644
--- a/libstdc++-v3/docs/html/17_intro/porting.texi
+++ b/libstdc++-v3/docs/html/17_intro/porting.texi
@@ -176,7 +176,7 @@ starting point.
@chapter Character types
The library requires that you provide three header files to implement
-character classification, analagous to that provided by the C libraries
+character classification, analogous to that provided by the C libraries
@file{exit(), f2 will be called, then
obj2 will be destroyed, then f1 will be called, and finally obj1
- will be destroyed. If f1 or f2 allow an exception to propogate
+ will be destroyed. If f1 or f2 allow an exception to propagate
out of them, Bad Things happen.
The standard exception classes carry with them a single string as data (usually describing what went wrong or where the 'throw' took place). It's good to remember that you can add your own data to - these exceptions when extending the heirarchy: + these exceptions when extending the hierarchy:
struct My_Exception : public std::runtime_error
diff --git a/libstdc++-v3/docs/html/20_util/howto.html b/libstdc++-v3/docs/html/20_util/howto.html
index 1d34b491467..d90b5d6654a 100644
--- a/libstdc++-v3/docs/html/20_util/howto.html
+++ b/libstdc++-v3/docs/html/20_util/howto.html
@@ -91,7 +91,7 @@
auto_ptr inside container classes
All of the containers
described in the standard library require their contained types
- to have, among other things, a copy contructor like this:
+ to have, among other things, a copy constructor like this:
struct My_Type
{
diff --git a/libstdc++-v3/docs/html/21_strings/howto.html b/libstdc++-v3/docs/html/21_strings/howto.html
index c9aabe017ae..6acd357c959 100644
--- a/libstdc++-v3/docs/html/21_strings/howto.html
+++ b/libstdc++-v3/docs/html/21_strings/howto.html
@@ -37,7 +37,7 @@
CString. Often programmers realize that a standard portable
answer is better than a proprietary nonportable one, but in porting
their application from a Win32 platform, they discover that they
- are relying on special functons offered by the CString class.
+ are relying on special functions offered by the CString class.
Return to top of page or
to the FAQ.
diff --git a/libstdc++-v3/docs/html/23_containers/howto.html b/libstdc++-v3/docs/html/23_containers/howto.html
index 8cdaab1615a..29c72185041 100644
--- a/libstdc++-v3/docs/html/23_containers/howto.html
+++ b/libstdc++-v3/docs/html/23_containers/howto.html
@@ -165,7 +165,7 @@
bitset
for the required number of bits, inside some wrapper functions with
unchanging signatures. Have your program then call the
- compiler on that file using Position Independant Code, then open the
+ compiler on that file using Position Independent Code, then open the
newly-created object file and load those wrapper functions. You'll have
an instantiation of bitset<N> for the exact
N
@@ -324,7 +324,7 @@
be the entry in the container pointed to by hint, that
is, h = *hint. Then the item being inserted should have
a key less than that of h, and greater than that of the
- item preceeding h. The new item will be inserted
+ item preceding h. The new item will be inserted
between h and h's predecessor.
diff --git a/libstdc++-v3/docs/html/26_numerics/howto.html b/libstdc++-v3/docs/html/26_numerics/howto.html
index 83614e6d86d..e15870f57bf 100644
--- a/libstdc++-v3/docs/html/26_numerics/howto.html
+++ b/libstdc++-v3/docs/html/26_numerics/howto.html
@@ -133,7 +133,7 @@
The C99 features depend on the --enable-c99 configure flag.
This flag is already on by default, but it can be disabled by the
user. Also, the configuration machinery will disable it if the
- neccessary support for C99 (e.g., header files) cannot be found.
+ necessary support for C99 (e.g., header files) cannot be found.
As of GCC 3.0, C99 support includes classification functions
such as isnormal, isgreater,
diff --git a/libstdc++-v3/docs/html/27_io/binary_iostreams_kuehl.txt b/libstdc++-v3/docs/html/27_io/binary_iostreams_kuehl.txt
index 901701ff480..44c78225306 100644
--- a/libstdc++-v3/docs/html/27_io/binary_iostreams_kuehl.txt
+++ b/libstdc++-v3/docs/html/27_io/binary_iostreams_kuehl.txt
@@ -80,7 +80,7 @@ on the streams level.
When I wrote the above paragraph about confirming your choice, I haven't
read this question! As I said above: You told us what solution you have
-choosen without stating what problem is solved. We cannot determine
+chosen without stating what problem is solved. We cannot determine
whether your choice is the right one. Actually, I'm pretty sure it is
the wrong one but without seen the details I can't be certain.
--
diff --git a/libstdc++-v3/docs/html/27_io/howto.html b/libstdc++-v3/docs/html/27_io/howto.html
index e83c2e6da49..23489525aa4 100644
--- a/libstdc++-v3/docs/html/27_io/howto.html
+++ b/libstdc++-v3/docs/html/27_io/howto.html
@@ -113,7 +113,7 @@
when the output stream is, in fact, a terminal and not a file
or some other device -- and that may not even be true
since C++ says nothing about files nor terminals. All of that is
- system-dependant. (The "newline-buffer-flushing only occuring
+ system-dependent. (The "newline-buffer-flushing only occurring
on terminals" thing is mostly true on Unix systems, though.)
Some people also believe that sending endl down an
@@ -167,7 +167,7 @@
arguments are the same as those for the Standard C I/O Library
function (a buffer area followed by its size).
- A great deal of this is implementation-dependant. For example,
+
A great deal of this is implementation-dependent. For example,
streambuf does not specify any actions for its own
setbuf()-ish functions; the classes derived from
streambuf each define behavior that "makes
@@ -183,7 +183,7 @@
A last reminder: there are usually more buffers involved than
just those at the language/library level. Kernel buffers, disk
buffers, and the like will also have an effect. Inspecting and
- changing those are system-dependant.
+ changing those are system-dependent.
Return to top of page or
to the FAQ.
@@ -445,7 +445,7 @@
You must do this before performing any I/O via the C++ stream objects.
- Once you call this, the C++ streams will operate independantly of the
+ Once you call this, the C++ streams will operate independently of the
(unused) C streams. For GCC 3.0, this means that cout and
company will become fully buffered on their own.
diff --git a/libstdc++-v3/docs/html/ext/sgiexts.html b/libstdc++-v3/docs/html/ext/sgiexts.html
index 62db99c0e4a..636f9f8b83b 100644
--- a/libstdc++-v3/docs/html/ext/sgiexts.html
+++ b/libstdc++-v3/docs/html/ext/sgiexts.html
@@ -25,7 +25,7 @@ libstdc++-v3
for a description). Not every chapter may have extensions, and the
extensions may come and go. Also, this page is incomplete because the
author is pressed for time. Check back often; the latest change was on
- $Date: 2001/10/09 20:18:13 $ (UTC).
+ $Date: 2001/10/11 18:41:47 $ (UTC).
Descriptions range from the scanty to the verbose. You should also check
@@ -83,7 +83,7 @@ libstdc++-v3
Chapter 23
-A few extensions and nods to backwards-compatability have been made with
+
A few extensions and nods to backwards-compatibility have been made with
containers. Those dealing with older SGI-style allocators are dealt with
elsewhere. The remaining ones all deal with bits:
diff --git a/libstdc++-v3/docs/html/faq/index.html b/libstdc++-v3/docs/html/faq/index.html
index e7da17e3083..7b587855372 100644
--- a/libstdc++-v3/docs/html/faq/index.html
+++ b/libstdc++-v3/docs/html/faq/index.html
@@ -137,7 +137,7 @@ http://gcc.gnu.org/onlinedocs/libstdc++/faq/.
(such as string, vector<>, iostreams,
and algorithms) will be freely available and fully compliant.
Programmers will no longer need to "roll their own"
- nor be worried about platform-specific incompatabilities.
+ nor be worried about platform-specific incompatibilities.
@@ -390,7 +390,7 @@ which is no longer available, thanks deja...-->
Since the goal of ISO Standardization is for all C++
implementations to be able to share code, the final libstdc++
- should, in theory, be useable under any ISO-compliant
+ should, in theory, be usable under any ISO-compliant
compiler. It will still be targeted and optimized for
GCC/g++, however.
diff --git a/libstdc++-v3/docs/html/faq/index.txt b/libstdc++-v3/docs/html/faq/index.txt
index 4b7487b86dd..9aff7fb2d67 100644
--- a/libstdc++-v3/docs/html/faq/index.txt
+++ b/libstdc++-v3/docs/html/faq/index.txt
@@ -89,7 +89,7 @@
That means that all of the Standard classes and functions (such as
string, vector<>, iostreams, and algorithms) will be freely available
and fully compliant. Programmers will no longer need to "roll their
- own" nor be worried about platform-specific incompatabilities.
+ own" nor be worried about platform-specific incompatibilities.
_________________________________________________________________
1.3 Who's in charge of it?
@@ -314,7 +314,7 @@
Since the goal of ISO Standardization is for all C++ implementations
to be able to share code, the final libstdc++ should, in theory, be
- useable under any ISO-compliant compiler. It will still be targeted
+ usable under any ISO-compliant compiler. It will still be targeted
and optimized for GCC/g++, however.
_________________________________________________________________
diff --git a/libstdc++-v3/include/bits/basic_file.h b/libstdc++-v3/include/bits/basic_file.h
index e7c220a3801..aa624eec448 100644
--- a/libstdc++-v3/include/bits/basic_file.h
+++ b/libstdc++-v3/include/bits/basic_file.h
@@ -254,7 +254,7 @@ namespace std
};
} // namespace std
-// Now include the bits that are dependant on the underlying I/O
+// Now include the bits that are dependent on the underlying I/O
// model chosen at configure time.
#include
diff --git a/libstdc++-v3/include/bits/locale_facets.h b/libstdc++-v3/include/bits/locale_facets.h
index 05b54c55cf5..8ea0ed547ef 100644
--- a/libstdc++-v3/include/bits/locale_facets.h
+++ b/libstdc++-v3/include/bits/locale_facets.h
@@ -502,7 +502,7 @@ namespace std
~_Format_cache() throw() { }
- // Given a member of the ios heirarchy as an argument, extract
+ // Given a member of the ios hierarchy as an argument, extract
// out all the current formatting information into a
// _Format_cache object and return a pointer to it.
static _Format_cache<_CharT>*
diff --git a/libstdc++-v3/include/bits/locale_facets.tcc b/libstdc++-v3/include/bits/locale_facets.tcc
index 0fe180b3486..b4c7f7c69e7 100644
--- a/libstdc++-v3/include/bits/locale_facets.tcc
+++ b/libstdc++-v3/include/bits/locale_facets.tcc
@@ -1841,7 +1841,7 @@ namespace std
// NB: In IEE 1003.1-200x, and perhaps other locale models, it
// is possible that the format character will be longer than one
// character. Possibilities include 'E' or 'O' followed by a
- // format charcter: if __mod is not the default argument, assume
+ // format character: if __mod is not the default argument, assume
// it's a valid modifier.
char_type __fmt[4];
__fmt[0] = __ctype.widen('%');
diff --git a/libstdc++-v3/include/bits/std_sstream.h b/libstdc++-v3/include/bits/std_sstream.h
index 1b8d5eff947..d36070a8abe 100644
--- a/libstdc++-v3/include/bits/std_sstream.h
+++ b/libstdc++-v3/include/bits/std_sstream.h
@@ -90,7 +90,7 @@ namespace std
if (_M_mode & ios_base::out)
{
// This is the deal: _M_string.size() is a value that
- // represents the size of the intial string that makes
+ // represents the size of the initial string that makes
// _M_string, and may not be the correct size of the
// current stringbuf internal buffer.
__size_type __len = _M_string.size();
diff --git a/libstdc++-v3/include/ext/ropeimpl.h b/libstdc++-v3/include/ext/ropeimpl.h
index b8f45688a58..4d15517845f 100644
--- a/libstdc++-v3/include/ext/ropeimpl.h
+++ b/libstdc++-v3/include/ext/ropeimpl.h
@@ -977,7 +977,7 @@ rope<_CharT,_Alloc>::_S_flatten(_RopeRep* __r, _CharT* __buffer)
}
case _RopeRep::_S_function:
case _RopeRep::_S_substringfn:
- // We dont yet do anything with substring nodes.
+ // We don't yet do anything with substring nodes.
// This needs to be fixed before ropefiles will work well.
{
_RopeFunction* __f = (_RopeFunction*)__r;
diff --git a/libstdc++-v3/include/ext/stl_rope.h b/libstdc++-v3/include/ext/stl_rope.h
index 00db893c923..72bdeb34373 100644
--- a/libstdc++-v3/include/ext/stl_rope.h
+++ b/libstdc++-v3/include/ext/stl_rope.h
@@ -340,7 +340,7 @@ identity_element(_Rope_Concat_fn<_CharT, _Alloc>)
// that doesn't work, since it makes it impossible to define generic
// equality on rope iterators. According to the draft standard, the
// template parameters for such an equality operator cannot be inferred
-// from the occurence of a member class as a parameter.
+// from the occurrence of a member class as a parameter.
// (SGI compilers in fact allow this, but the __result wouldn't be
// portable.)
// Similarly, some of the static member functions are member functions
@@ -543,7 +543,7 @@ struct _Rope_RopeLeaf : public _Rope_RopeRep<_CharT,_Alloc> {
public:
// Apparently needed by VC++
// The data fields of leaves are allocated with some
- // extra space, to accomodate future growth and for basic
+ // extra space, to accommodate future growth and for basic
// character types, to hold a trailing eos character.
enum { _S_alloc_granularity = 8 };
static size_t _S_rounded_up_size(size_t __n) {
@@ -845,7 +845,7 @@ class _Rope_iterator_base
public:
typedef _Alloc _allocator_type; // used in _Rope_rotate, VC++ workaround
typedef _Rope_RopeRep<_CharT,_Alloc> _RopeRep;
- // Borland doesnt want this to be protected.
+ // Borland doesn't want this to be protected.
protected:
enum { _S_path_cache_len = 4 }; // Must be <= 9.
enum { _S_iterator_buf_len = 15 };
@@ -1321,7 +1321,7 @@ class rope : public _Rope_base<_CharT,_Alloc> {
const _CharT* __iter, size_t __slen)
// As above, but one reference to __r is about to be
// destroyed. Thus the pieces may be recycled if all
- // relevent reference counts are 1.
+ // relevant reference counts are 1.
# ifdef __GC
// We can't really do anything since refcounts are unavailable.
{ return _S_concat_char_iter(__r, __iter, __slen); }
diff --git a/libstdc++-v3/libsupc++/cxxabi.h b/libstdc++-v3/libsupc++/cxxabi.h
index e695ce5a223..dd6b774116e 100644
--- a/libstdc++-v3/libsupc++/cxxabi.h
+++ b/libstdc++-v3/libsupc++/cxxabi.h
@@ -45,7 +45,7 @@
#ifdef __cplusplus
// We use the compiler builtins __SIZE_TYPE__ and __PTRDIFF_TYPE__ instead of
-// std::size_t and std::ptrdiff_t respectively. This makes us independant of
+// std::size_t and std::ptrdiff_t respectively. This makes us independent of
// the conformance level of and whether -fhonor-std was supplied.
// is not currently available during compiler building anyway.
// Including would be wrong, as that would rudely place size_t in
@@ -363,7 +363,7 @@ protected:
class __vmi_class_type_info : public __class_type_info {
/* abi defined member variables */
public:
- unsigned int __flags; /* details about the class heirarchy */
+ unsigned int __flags; /* details about the class hierarchy */
unsigned int __base_count; /* number of direct bases */
__base_class_info const __base_info[1]; /* array of bases */
/* The array of bases uses the trailing array struct hack
diff --git a/libstdc++-v3/libsupc++/eh_throw.cc b/libstdc++-v3/libsupc++/eh_throw.cc
index a8e9ba34557..407b829f24b 100644
--- a/libstdc++-v3/libsupc++/eh_throw.cc
+++ b/libstdc++-v3/libsupc++/eh_throw.cc
@@ -40,7 +40,7 @@ __gxx_exception_cleanup (_Unwind_Reason_Code code, _Unwind_Exception *exc)
{
__cxa_exception *header = __get_exception_header_from_ue (exc);
- // If we havn't been caught by a foreign handler, then this is
+ // If we haven't been caught by a foreign handler, then this is
// some sort of unwind error. In that case just die immediately.
if (code != _URC_FOREIGN_EXCEPTION_CAUGHT)
__terminate (header->terminateHandler);
diff --git a/libstdc++-v3/libsupc++/tinfo.cc b/libstdc++-v3/libsupc++/tinfo.cc
index 732609cf048..8559a25a039 100644
--- a/libstdc++-v3/libsupc++/tinfo.cc
+++ b/libstdc++-v3/libsupc++/tinfo.cc
@@ -172,12 +172,12 @@ __vmi_class_type_info::
{}
// __upcast_result is used to hold information during traversal of a class
-// heirarchy when catch matching.
+// hierarchy when catch matching.
struct __class_type_info::__upcast_result
{
const void *dst_ptr; // pointer to caught object
__sub_kind part2dst; // path from current base to target
- int src_details; // hints about the source type heirarchy
+ int src_details; // hints about the source type hierarchy
const __class_type_info *base_type; // where we found the target,
// if in vbase the __class_type_info of vbase
// if a non-virtual base then 1
@@ -189,14 +189,14 @@ struct __class_type_info::__upcast_result
};
// __dyncast_result is used to hold information during traversal of a class
-// heirarchy when dynamic casting.
+// hierarchy when dynamic casting.
struct __class_type_info::__dyncast_result
{
const void *dst_ptr; // pointer to target object or NULL
__sub_kind whole2dst; // path from most derived object to target
__sub_kind whole2src; // path from most derived object to sub object
__sub_kind dst2src; // path from target to sub object
- int whole_details; // details of the whole class heirarchy
+ int whole_details; // details of the whole class hierarchy
public:
__dyncast_result (int details_ = __vmi_class_type_info::__flags_unknown_mask)
@@ -483,7 +483,7 @@ __do_dyncast (ptrdiff_t src2dst,
|| !(result.whole_details & __diamond_shaped_mask)))
{
// We already found SRC_PTR as a base of most derived, and
- // either it was non-virtual, or the whole heirarchy is
+ // either it was non-virtual, or the whole hierarchy is
// not-diamond shaped. Therefore if it is in either choice, it
// can only be in one of them, and we will already know.
if (old_sub_kind == __unknown)
diff --git a/libstdc++-v3/libsupc++/typeinfo b/libstdc++-v3/libsupc++/typeinfo
index a1d62c3d791..3d9afc90470 100644
--- a/libstdc++-v3/libsupc++/typeinfo
+++ b/libstdc++-v3/libsupc++/typeinfo
@@ -90,7 +90,7 @@ namespace std
// type. Uniqueness must use the _name value, not object address.
bool operator==(const type_info& __arg) const;
#else
- /** Returns true if @c *this preceeds @c __arg in the implementation's
+ /** Returns true if @c *this precedes @c __arg in the implementation's
* collation order. */
// In new abi we can rely on type_info's NTBS being unique,
// and therefore address comparisons are sufficient.
diff --git a/libstdc++-v3/testsuite/24_iterators/iterator.cc b/libstdc++-v3/testsuite/24_iterators/iterator.cc
index a5a6974f80a..98aa8c0b258 100644
--- a/libstdc++-v3/testsuite/24_iterators/iterator.cc
+++ b/libstdc++-v3/testsuite/24_iterators/iterator.cc
@@ -1,4 +1,4 @@
-// 24.1.5 Random accesss iterators
+// 24.1.5 Random access iterators
// 24.3.1 Iterator traits
// (basic_string and vector implementations)
//
--
2.30.2