summaryrefslogtreecommitdiff
path: root/gcc/cp/gxxint.texi
diff options
context:
space:
mode:
authorkenner <kenner@138bc75d-0d04-0410-961f-82ee72b054a4>1995-08-28 10:54:22 +0000
committerkenner <kenner@138bc75d-0d04-0410-961f-82ee72b054a4>1995-08-28 10:54:22 +0000
commitb090827b2632f1f1d90adf6ed537bcaa76381190 (patch)
tree1c83e6e4689be8894157ee8b0f76e689bf3b8871 /gcc/cp/gxxint.texi
parentd217a1ad3cab054b26557a021afa46aad06cff45 (diff)
downloadgcc-b090827b2632f1f1d90adf6ed537bcaa76381190.tar.gz
Fix spelling errors.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@10289 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/cp/gxxint.texi')
-rw-r--r--gcc/cp/gxxint.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/cp/gxxint.texi b/gcc/cp/gxxint.texi
index 2db1dc9285f..f307babbca4 100644
--- a/gcc/cp/gxxint.texi
+++ b/gcc/cp/gxxint.texi
@@ -1214,7 +1214,7 @@ nop, if they are the same size.
When we invoke the copy constructor for an exception object because it
is passed by value, and if we take a hit (exception) inside the copy
-constructor someplace, where do we go? I have tentatively choosen to
+constructor someplace, where do we go? I have tentatively chosen to
not catch throws by the outer block at the same unwind level, if one
exists, but rather to allow the frame to unwind into the next series of
handlers, if any. If this is the wrong way to do it, we will need to