From 7584a3f96de88d5eefe5d6c634515278cbfbf052 Mon Sep 17 00:00:00 2001 From: Florian Weimer Date: Sat, 20 Feb 2016 12:56:55 +0100 Subject: Deprecate readdir_r, readdir64_r [BZ #19056] --- manual/filesys.texi | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) (limited to 'manual/filesys.texi') diff --git a/manual/filesys.texi b/manual/filesys.texi index 972e106..b323664 100644 --- a/manual/filesys.texi +++ b/manual/filesys.texi @@ -525,8 +525,9 @@ locking. Like @code{readdir} it returns the next entry from the directory. To prevent conflicts between simultaneously running threads the result is stored inside the @var{entry} object. -@strong{Portability Note:} It is recommended to use @code{readdir} -instead of @code{readdir_r} for the following reasons: +@strong{Portability Note:} @code{readdir_r} is deprecated. It is +recommended to use @code{readdir} instead of @code{readdir_r} for the +following reasons: @itemize @bullet @item @@ -604,10 +605,10 @@ In all other aspects this function is equivalent to @code{readdir}. @comment LFS @deftypefun int readdir64_r (DIR *@var{dirstream}, struct dirent64 *@var{entry}, struct dirent64 **@var{result}) @safety{@prelim{}@mtsafe{}@asunsafe{@asulock{}}@acunsafe{@aculock{}}} -The @code{readdir64_r} function is equivalent to the @code{readdir_r} -function except that it takes parameters of base type @code{struct -dirent64} instead of @code{struct dirent} in the second and third -position. The same precautions mentioned in the documentation of +The deprecated @code{readdir64_r} function is equivalent to the +@code{readdir_r} function except that it takes parameters of base type +@code{struct dirent64} instead of @code{struct dirent} in the second and +third position. The same precautions mentioned in the documentation of @code{readdir_r} also apply here. @end deftypefun -- cgit v1.1