diff options
| author | Joseph Myers <jsm28@cam.ac.uk> | 2001-11-23 16:29:02 +0000 |
|---|---|---|
| committer | Joseph Myers <jsm28@gcc.gnu.org> | 2001-11-23 16:29:02 +0000 |
| commit | c5504edb751bff4f5b2a493921466d04857494f4 (patch) | |
| tree | 0964bed1b243c87e49965682c6ac6d686a4f5186 /libstdc++-v3/docs | |
| parent | eac50d7a73bbc070770fbe81e837dbd589f5869c (diff) | |
| download | gcc-c5504edb751bff4f5b2a493921466d04857494f4.zip gcc-c5504edb751bff4f5b2a493921466d04857494f4.tar.gz gcc-c5504edb751bff4f5b2a493921466d04857494f4.tar.bz2 | |
ChangeLog, [...]: Fix spelling errors.
* ChangeLog, docs/doxygen/maint.cfg.in, docs/doxygen/user.cfg.in,
docs/doxygen/doxygroups.cc, docs/doxygen/Intro.3,
docs/html/17_intro/BUGS, docs/html/17_intro/C++STYLE,
docs/html/17_intro/CHECKLIST, docs/html/17_intro/DESIGN,
docs/html/17_intro/howto.html, docs/html/17_intro/porting.html,
docs/html/17_intro/porting.texi, docs/html/18_support/howto.html,
docs/html/19_diagnostics/howto.html, docs/html/20_util/howto.html,
docs/html/21_strings/howto.html,
docs/html/23_containers/howto.html,
docs/html/26_numerics/howto.html, docs/html/27_io/howto.html,
docs/html/27_io/binary_iostreams_kuehl.txt,
docs/html/ext/sgiexts.html, docs/html/faq/index.html,
docs/html/faq/index.txt, testsuite/24_iterators/iterator.cc,
include/bits/basic_file.h, include/bits/locale_facets.h,
include/bits/locale_facets.tcc, include/bits/std_sstream.h,
include/ext/ropeimpl.h, include/ext/stl_rope.h,
libsupc++/tinfo.cc, libsupc++/cxxabi.h, libsupc++/typeinfo,
libsupc++/eh_throw.cc, acinclude.m4, aclocal.m4, configure,
configure.target, ChangeLog-2000: Fix spelling errors.
From-SVN: r47291
Diffstat (limited to 'libstdc++-v3/docs')
22 files changed, 36 insertions, 36 deletions
diff --git a/libstdc++-v3/docs/doxygen/Intro.3 b/libstdc++-v3/docs/doxygen/Intro.3 index b54bd55..52998c9 100644 --- a/libstdc++-v3/docs/doxygen/Intro.3 +++ b/libstdc++-v3/docs/doxygen/Intro.3 @@ -66,7 +66,7 @@ lB lB lB lB. <complex> <fstream> <memory> <vector> <csetjmp> <functional> <numeric> .TE -.SS Backwards-Compatability Headers +.SS Backwards-Compatibility Headers For GCC 3.0 these headers will be found automatically, unless you instruct the compiler otherwise. You should not depend on this, instead you should read FAQ 5.4 and use a diff --git a/libstdc++-v3/docs/doxygen/doxygroups.cc b/libstdc++-v3/docs/doxygen/doxygroups.cc index 72e5ef3..de304f1 100644 --- a/libstdc++-v3/docs/doxygen/doxygroups.cc +++ b/libstdc++-v3/docs/doxygen/doxygroups.cc @@ -67,7 +67,7 @@ following: As an example of the first case, @c vector is required to use a contiguous memory layout, while other sequences such as @c deque are not. -The prime reason for chosing one sequence over another should be based on +The prime reason for choosing one sequence over another should be based on the second category of differences, algorithmic complexity. For example, if you need to perform many inserts and removals from the middle of a sequence, @c list would be ideal. But if you need to perform constant-time access to diff --git a/libstdc++-v3/docs/doxygen/maint.cfg.in b/libstdc++-v3/docs/doxygen/maint.cfg.in index 10c43d4..71801e6 100644 --- a/libstdc++-v3/docs/doxygen/maint.cfg.in +++ b/libstdc++-v3/docs/doxygen/maint.cfg.in @@ -140,7 +140,7 @@ STRIP_CODE_COMMENTS = YES # file names in lower case letters. If set to YES upper case letters are also # allowed. This is useful if you have classes or files whose names only differ # in case and if your file system supports case sensitive file names. Windows -# users are adviced to set this option to NO. +# users are advised to set this option to NO. CASE_SENSE_NAMES = YES diff --git a/libstdc++-v3/docs/doxygen/user.cfg.in b/libstdc++-v3/docs/doxygen/user.cfg.in index a78cd5c..b9d192a 100644 --- a/libstdc++-v3/docs/doxygen/user.cfg.in +++ b/libstdc++-v3/docs/doxygen/user.cfg.in @@ -144,7 +144,7 @@ STRIP_CODE_COMMENTS = YES # file names in lower case letters. If set to YES upper case letters are also # allowed. This is useful if you have classes or files whose names only differ # in case and if your file system supports case sensitive file names. Windows -# users are adviced to set this option to NO. +# users are advised to set this option to NO. CASE_SENSE_NAMES = NO diff --git a/libstdc++-v3/docs/html/17_intro/BUGS b/libstdc++-v3/docs/html/17_intro/BUGS index 1505035..04e4bc8 100644 --- a/libstdc++-v3/docs/html/17_intro/BUGS +++ b/libstdc++-v3/docs/html/17_intro/BUGS @@ -5,7 +5,7 @@ - _GLIBCPP_HAS_BUILTIN_SINF: We should still hold out for a cleaner solution the is currenly the case in bits/std_cmath.h. -- there may be one set of remaining string bugs, dependant on final +- there may be one set of remaining string bugs, dependent on final clarification of the string::find technicalities when finding in an empty string or using an empty string for an argument. At the very least, v-3 has interpreted the standard in a way that is in opposition diff --git a/libstdc++-v3/docs/html/17_intro/C++STYLE b/libstdc++-v3/docs/html/17_intro/C++STYLE index 5d22d7e..46fe3f3 100644 --- a/libstdc++-v3/docs/html/17_intro/C++STYLE +++ b/libstdc++-v3/docs/html/17_intro/C++STYLE @@ -122,7 +122,7 @@ Notable areas of divergence from what may be previous local practice // } -09. Member functions declarations and defintions +09. Member functions declarations and definitions Keywords such as extern, static, export, explicit, inline, etc go on the line above the function name. Thus diff --git a/libstdc++-v3/docs/html/17_intro/CHECKLIST b/libstdc++-v3/docs/html/17_intro/CHECKLIST index bef9635..9d3f80d 100644 --- a/libstdc++-v3/docs/html/17_intro/CHECKLIST +++ b/libstdc++-v3/docs/html/17_intro/CHECKLIST @@ -958,7 +958,7 @@ T X* get() const throw(); T X* release() throw(); T void reset(X* p =0) throw(); - // _lib.auto.ptr.conv_ converions: + // _lib.auto.ptr.conv_ conversions: X auto_ptr(auto_ptr_ref<X>) throw(); X template<class Y> operator auto_ptr_ref<Y>() throw(); X template<class Y> operator auto_ptr<Y>() throw(); diff --git a/libstdc++-v3/docs/html/17_intro/DESIGN b/libstdc++-v3/docs/html/17_intro/DESIGN index 6979bc4..5af3d9a 100644 --- a/libstdc++-v3/docs/html/17_intro/DESIGN +++ b/libstdc++-v3/docs/html/17_intro/DESIGN @@ -253,7 +253,7 @@ cases it may actually be excessive. To implement a library which does not use exceptions directly is not difficult given minor compiler support (to "turn off" exceptions -and ignore exception contructs), and results in no great library +and ignore exception constructs), and results in no great library maintenance difficulties. To be precise, given "-fno-exceptions", the compiler should treat "try" blocks as ordinary blocks, and "catch" blocks as dead code to ignore or eliminate. Compiler diff --git a/libstdc++-v3/docs/html/17_intro/howto.html b/libstdc++-v3/docs/html/17_intro/howto.html index c4bfcc3..3dce6f9 100644 --- a/libstdc++-v3/docs/html/17_intro/howto.html +++ b/libstdc++-v3/docs/html/17_intro/howto.html @@ -124,7 +124,7 @@ </p> <p>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. <ul> @@ -142,7 +142,7 @@ (A large selection of links to older messages has been removed; many of the messages from 1999 were lost in a disk crash, and the few people with access to the backup tapes have been too swamped with work - to restore them. Many of the points have been superceded anyhow.) + to restore them. Many of the points have been superseded anyhow.) </p> <p>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 291393c..344fb4f 100644 --- a/libstdc++-v3/docs/html/17_intro/porting.html +++ b/libstdc++-v3/docs/html/17_intro/porting.html @@ -140,7 +140,7 @@ Up:<a rel=up href="#Top">Top</a> <h1>Character types</h1> <p>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 <code><ctype.h></code> header. You can model these on the files provided in <code>config/os/generic/bits</code>. 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 <code><ctype.h></code> 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 <code>bits/ctype_base.h</code> file gives the type of the integer, and the values of the various bit masks. You will have to peer at your own <code><ctype.h></code> to figure out @@ -273,7 +273,7 @@ contains a few more functions. On most systems, you can just copy <code>config/os/generic/ctype_inline.h</code> and use it on your system. <p>In detail, the functions provided test characters for particular -properties; they are analagous to the functions like <code>isalpha</code> and +properties; they are analogous to the functions like <code>isalpha</code> and <code>islower</code> provided by the C library. <p>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 018cbde..d5d32b4 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{<ctype.h>} header. You can model these on the files provided in @file{config/os/generic/bits}. However, these files will almost certainly need some modification. @@ -185,7 +185,7 @@ The first file to write is @file{bits/ctype_base.h}. This file provides some very basic information about character classification. The libstdc++-v3 library assumes that your C library implements @file{<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 @file{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 @file{<ctype.h>} to figure out @@ -316,7 +316,7 @@ contains a few more functions. On most systems, you can just copy @file{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 @code{isalpha} and +properties; they are analogous to the functions like @code{isalpha} and @code{islower} provided by the C library. The first function is implemented like this on IRIX: diff --git a/libstdc++-v3/docs/html/18_support/howto.html b/libstdc++-v3/docs/html/18_support/howto.html index ec7a2d0..13adbfd 100644 --- a/libstdc++-v3/docs/html/18_support/howto.html +++ b/libstdc++-v3/docs/html/18_support/howto.html @@ -182,7 +182,7 @@ atexit(f2); </pre>then at a call of <code>exit()</code>, 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. </ol> </p> diff --git a/libstdc++-v3/docs/html/19_diagnostics/howto.html b/libstdc++-v3/docs/html/19_diagnostics/howto.html index d30b5d9..e85d57d 100644 --- a/libstdc++-v3/docs/html/19_diagnostics/howto.html +++ b/libstdc++-v3/docs/html/19_diagnostics/howto.html @@ -37,7 +37,7 @@ <p>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: </p> <pre> 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 1d34b49..d90b5d6 100644 --- a/libstdc++-v3/docs/html/20_util/howto.html +++ b/libstdc++-v3/docs/html/20_util/howto.html @@ -91,7 +91,7 @@ <h2><a name="2"><code>auto_ptr</code> inside container classes</a></h2> <p>All of the <a href="../23_containers/howto.html">containers</a> 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: <pre> struct My_Type { diff --git a/libstdc++-v3/docs/html/21_strings/howto.html b/libstdc++-v3/docs/html/21_strings/howto.html index c9aabe0..6acd357 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. </p> <p>Things are not as bad as they seem. In <a href="http://gcc.gnu.org/ml/gcc/1999-04n/msg00236.html">this @@ -58,7 +58,7 @@ stringstream classes. These are the bridge between the iostream hierarchy and the string class, and they operate with regular streams seamlessly because they inherit from the iostream - heirarchy. An quick example: + hierarchy. An quick example: <pre> #include <iostream> #include <string> @@ -315,7 +315,7 @@ str.erase(notwhite+1); </pre> Obviously, the calls to <code>find</code> could be inserted directly into the calls to <code>erase</code>, in case your compiler does not - optimize named temporaries out of existance. + optimize named temporaries out of existence. </p> <p>Return <a href="#top">to top of page</a> or <a href="../faq/index.html">to the FAQ</a>. diff --git a/libstdc++-v3/docs/html/23_containers/howto.html b/libstdc++-v3/docs/html/23_containers/howto.html index 8cdaab1..29c7218 100644 --- a/libstdc++-v3/docs/html/23_containers/howto.html +++ b/libstdc++-v3/docs/html/23_containers/howto.html @@ -165,7 +165,7 @@ <code>bitset</code> 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 <code>bitset<N></code> for the exact <code>N</code> @@ -324,7 +324,7 @@ be the entry in the container pointed to by <code>hint</code>, that is, <code>h = *hint</code>. Then the item being inserted should have a key less than that of <code>h</code>, and greater than that of the - item preceeding <code>h</code>. The new item will be inserted + item preceding <code>h</code>. The new item will be inserted between <code>h</code> and <code>h</code>'s predecessor. </ul> </p> diff --git a/libstdc++-v3/docs/html/26_numerics/howto.html b/libstdc++-v3/docs/html/26_numerics/howto.html index 83614e6..e15870f 100644 --- a/libstdc++-v3/docs/html/26_numerics/howto.html +++ b/libstdc++-v3/docs/html/26_numerics/howto.html @@ -133,7 +133,7 @@ <p>The C99 features depend on the <code>--enable-c99</code> 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. </p> <p>As of GCC 3.0, C99 support includes classification functions such as <code>isnormal</code>, <code>isgreater</code>, 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 901701f..44c7822 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 e83c2e6..2348952 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 <em>that</em> 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.) </p> <p>Some people also believe that sending <code>endl</code> 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). </p> - <p>A great deal of this is implementation-dependant. For example, + <p>A great deal of this is implementation-dependent. For example, <code>streambuf</code> does not specify any actions for its own <code>setbuf()</code>-ish functions; the classes derived from <code>streambuf</code> each define behavior that "makes @@ -183,7 +183,7 @@ <p>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. </p> <p>Return <a href="#top">to top of page</a> or <a href="../faq/index.html">to the FAQ</a>. @@ -445,7 +445,7 @@ </pre> </p> <p>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 <code>cout</code> and company will become fully buffered on their own. </p> diff --git a/libstdc++-v3/docs/html/ext/sgiexts.html b/libstdc++-v3/docs/html/ext/sgiexts.html index 62db99c..636f9f8 100644 --- a/libstdc++-v3/docs/html/ext/sgiexts.html +++ b/libstdc++-v3/docs/html/ext/sgiexts.html @@ -25,7 +25,7 @@ libstdc++-v3</a></h1> 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). </p> <p>Descriptions range from the scanty to the verbose. You should also check @@ -83,7 +83,7 @@ libstdc++-v3</a></h1> <hr> <a name="ch23"><h3>Chapter 23</h3></a> -<p>A few extensions and nods to backwards-compatability have been made with +<p>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: </p> diff --git a/libstdc++-v3/docs/html/faq/index.html b/libstdc++-v3/docs/html/faq/index.html index e7da17e..7b58785 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/</a>.</p> (such as <code>string</code>, <code>vector<></code>, 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. </p> <hr> @@ -390,7 +390,7 @@ which is no longer available, thanks deja...--> </p> <p>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. </p> diff --git a/libstdc++-v3/docs/html/faq/index.txt b/libstdc++-v3/docs/html/faq/index.txt index 4b7487b..9aff7fb 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. _________________________________________________________________ |