summaryrefslogtreecommitdiff
path: root/man3/fmemopen.3
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2006-04-20 20:20:01 +0000
committerMichael Kerrisk <mtk.manpages@gmail.com>2006-04-20 20:20:01 +0000
commitb776661a6546ea37bec9e12041d07d0cfb4e0e61 (patch)
treed400150ff72a1201d6d6b0291c4317ffbb39af63 /man3/fmemopen.3
parent97b6cd4152404eb94f1c5217e66967791dd2cb7b (diff)
Updated FIXME
Diffstat (limited to 'man3/fmemopen.3')
-rw-r--r--man3/fmemopen.34
1 files changed, 3 insertions, 1 deletions
diff --git a/man3/fmemopen.3 b/man3/fmemopen.3
index af5e1df5d..3a7311270 100644
--- a/man3/fmemopen.3
+++ b/man3/fmemopen.3
@@ -65,7 +65,9 @@ of the buffer's size, using
.\" see http://sourceware.org/bugzilla/show_bug.cgi?id=1995
.\" FIXME it is possible that the glibc fmemopen() implementation
.\" may eventually include an implicit setbuffer() call so that
-.\" the above behaviour is the default. mtk, Apr 2006.
+.\" the above behaviour is the default, see:
+.\" http://sources.redhat.com/ml/libc-alpha/2006-04/msg00063.html
+.\" mtk, Apr 2006
.PP
In a stream opened for reading,
null bytes ('\\0') in the buffer do not cause read