summaryrefslogtreecommitdiff
path: root/lib
diff options
context:
space:
mode:
authorJim Meyering <jim@meyering.net>2005-07-04 17:39:48 +0000
committerJim Meyering <jim@meyering.net>2005-07-04 17:39:48 +0000
commite2b7434615ff8ad9fd37c93d0c563976fa59daf8 (patch)
tree5f23c9cd68ab5e572cb8f9873d84410712b80825 /lib
parent14ad8a2da743338e4b1b319f0db3dafff01bebe1 (diff)
downloadcoreutils-e2b7434615ff8ad9fd37c93d0c563976fa59daf8.tar.xz
rename: s/verify_dcl/verify_decl/
Diffstat (limited to 'lib')
-rw-r--r--lib/verify.h10
1 files changed, 5 insertions, 5 deletions
diff --git a/lib/verify.h b/lib/verify.h
index 013ed84f8..b86acaea9 100644
--- a/lib/verify.h
+++ b/lib/verify.h
@@ -19,21 +19,21 @@
#ifndef VERIFY_H
# define VERIFY_H 1
-# ifndef verify_dcl
+# ifndef verify_decl
# define GL_CONCAT0(x, y) x##y
# define GL_CONCAT(x, y) GL_CONCAT0 (x, y)
/* Verify requirement, R, at compile-time, as a declaration.
The implementation uses a struct declaration whose name includes the
expansion of __LINE__, so there is a small chance that two uses of
- verify_dcl from different files will end up colliding (for example,
- f.c includes f.h and verify_dcl is used on the same line in each). */
-# define verify_dcl(R) \
+ verify_decl from different files will end up colliding (for example,
+ f.c includes f.h and verify_decl is used on the same line in each). */
+# define verify_decl(R) \
struct GL_CONCAT (ct_assert_, __LINE__) { char a[(R) ? 1 : -1]; }
# endif
/* Verify requirement, R, at compile-time, as an expression.
- Unlike assert, there is no run-time overhead. Unlike verify_dcl,
+ Unlike assert, there is no run-time overhead. Unlike verify_decl,
above, there is no risk of collision, since there is no declared name.
This macro may be used in some contexts where the other may not, and
vice versa. Return void. */