aboutsummaryrefslogtreecommitdiffstats
path: root/man3
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2008-11-14 11:57:50 -0500
committerMichael Kerrisk <mtk.manpages@gmail.com>2008-11-25 20:54:01 -0500
commitf4efb1e28b6948fb8907b6fd8893baaae198b0c0 (patch)
tree9f5048f0bceeebf14188a577510c1b21eada0ed0 /man3
parent6ee1c2aaf569546cc257ef1b15cb3fb3aaeb9834 (diff)
downloadman-pages-f4efb1e28b6948fb8907b6fd8893baaae198b0c0.tar.gz
CPU_SET.3: NOTES: Discuss use of types in "prototypes" for these macros
The SYNOPSIS shows types for arguments and return values, but these are really just suggestions: since the interfaces are macros, the compiler won't catch all violations of the "type rules". Warn the reader of this. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat (limited to 'man3')
-rw-r--r--man3/CPU_SET.36
1 files changed, 6 insertions, 0 deletions
diff --git a/man3/CPU_SET.3 b/man3/CPU_SET.3
index 285c40f4db..8558e92ea0 100644
--- a/man3/CPU_SET.3
+++ b/man3/CPU_SET.3
@@ -284,6 +284,12 @@ while the
argument of the
.BR CPU_*_S ()
macros is a size in bytes.
+
+The data types for arguments and return values shown
+in the SYNOPSIS are hints what about is expected in each case.
+However, since these these interfaces are implemented as macros,
+the compiler won't necessarily catch all type errors
+if you violate the suggestions.
.SH EXAMPLE
The following program demonstrates the use of some of the macros
used for dynamically allocated CPU sets.