comparison doc/posix-headers/stdnoreturn.texi @ 17331:bfb7633de5b0

Fix typo in stdnoreturn documentation.
author Paul Eggert <eggert@cs.ucla.edu>
date Tue, 19 Feb 2013 12:30:32 -0800
parents aa2fec6b7d37
children 33db65a13e67
comparison
equal deleted inserted replaced
17330:6f8d1926ece8 17331:bfb7633de5b0
26 problems with standard headers that use @code{__declspec (noreturn)} 26 problems with standard headers that use @code{__declspec (noreturn)}
27 directly. Although the resulting code operates correctly, the 27 directly. Although the resulting code operates correctly, the
28 compiler is not informed whether @code{noreturn} functions do not 28 compiler is not informed whether @code{noreturn} functions do not
29 return, so it may generate incorrect warnings at compile-time, or code 29 return, so it may generate incorrect warnings at compile-time, or code
30 that is slightly less optimized. This problem does not occur with 30 that is slightly less optimized. This problem does not occur with
31 @code{_Noreturn}.
31 @item 32 @item
32 Circa 2012 bleeding-edge GCC with @code{-Werror=old-style-declaration} 33 Circa 2012 bleeding-edge GCC with @code{-Werror=old-style-declaration}
33 requires @code{_Noreturn} or @code{noreturn} before the returned type 34 requires @code{_Noreturn} or @code{noreturn} before the returned type
34 in a declaration, and therefore rejects valid but unusually-worded 35 in a declaration, and therefore rejects valid but unusually-worded
35 declarations such as @code{void _Noreturn foo (void);}. 36 declarations such as @code{void _Noreturn foo (void);}.