aboutsummaryrefslogtreecommitdiff
path: root/gcc/extend.texi
diff options
context:
space:
mode:
authorAndreas Jaeger <aj@gcc.gnu.org>2001-02-22 16:41:49 +0100
committerAndreas Jaeger <aj@gcc.gnu.org>2001-02-22 16:41:49 +0100
commit3844cd2e43cc40dbbaedc6e900be59ad5f4b3cfc (patch)
tree7e9a5344dc1e1b3c89fc92de77a0c0b9adf24747 /gcc/extend.texi
parent9c96f3f85ed80d33f75191db9209ee7a7870e16e (diff)
downloadgcc-3844cd2e43cc40dbbaedc6e900be59ad5f4b3cfc.zip
gcc-3844cd2e43cc40dbbaedc6e900be59ad5f4b3cfc.tar.gz
gcc-3844cd2e43cc40dbbaedc6e900be59ad5f4b3cfc.tar.bz2
* extend.texi (C++ Attributes): Fix typo.
From-SVN: r39982
Diffstat (limited to 'gcc/extend.texi')
-rw-r--r--gcc/extend.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/extend.texi b/gcc/extend.texi
index c2ce6a3..3319cca 100644
--- a/gcc/extend.texi
+++ b/gcc/extend.texi
@@ -4321,7 +4321,7 @@ In Standard C++, objects defined at namespace scope are guaranteed to be
initialized in an order in strict accordance with that of their definitions
@emph{in a given translation unit}. No guarantee is made for initializations
across translation units. However, GNU C++ allows users to control the
-order of initialization of objects defined at namespace socpe with the
+order of initialization of objects defined at namespace scope with the
@code{init_priority} attribute by specifying a relative @var{priority},
a constant integral expression currently bounded between 101 and 65535
inclusive. Lower numbers indicate a higher priority.