X-Git-Url: https://erislabs.net/gitweb/?a=blobdiff_plain;f=doc%2Fverify.texi;h=df721d9c9a8b69873637ae4e6b799ce52c28c691;hb=b28ec8ed78286cbd1d113d0785e0e1f5cf11832e;hp=5fa8b147d7c7ca37a240d63fe7a692c0a6104d7e;hpb=0e24c5989ff4b5f886f10ad2b066d793caca7ff2;p=gnulib.git

diff --git a/doc/verify.texi b/doc/verify.texi
index 5fa8b147d..df721d9c9 100644
--- a/doc/verify.texi
+++ b/doc/verify.texi
@@ -1,6 +1,6 @@
 @c GNU verify module documentation
 
-@c Copyright (C) 2006, 2009-2011 Free Software Foundation, Inc.
+@c Copyright (C) 2006, 2009-2013 Free Software Foundation, Inc.
 
 @c Permission is granted to copy, distribute and/or modify this document
 @c under the terms of the GNU Free Documentation License, Version 1.3
@@ -50,11 +50,11 @@ integer constant expression, then a compiler might reject a usage like
 @samp{verify (@var{V});} even when @var{V} is
 nonzero.
 
-Although the standard @code{assert} macro is a runtime test, draft C1X
+Although the standard @code{assert} macro is a runtime test, C11
 specifies a builtin @code{_Static_assert (@var{V},
 @var{STRING-LITERAL})}, its @file{assert.h} header has a similar macro
-named @code{static_assert}, and draft C++0X has a similar
-@code{static_assert} builtin.  These draft builtins and macros differ
+named @code{static_assert}, and C++11 has a similar
+@code{static_assert} builtin.  These builtins and macros differ
 from @code{verify} in two major ways.  First, they can also be used
 within a @code{struct} or @code{union} specifier, in place of an
 ordinary member declaration.  Second, they require the programmer to