Commit 6df3fd37 authored by Georg Brandl's avatar Georg Brandl

bug [ 1186072 ] tempnam doc doesn't include link to tmpfile

parent e21d9ab3
...@@ -1101,8 +1101,8 @@ On \UNIX, the environment variable \envvar{TMPDIR} overrides ...@@ -1101,8 +1101,8 @@ On \UNIX, the environment variable \envvar{TMPDIR} overrides
behavior of this function depends on the C library implementation; behavior of this function depends on the C library implementation;
some aspects are underspecified in system documentation. some aspects are underspecified in system documentation.
\warning{Use of \function{tempnam()} is vulnerable to symlink attacks; \warning{Use of \function{tempnam()} is vulnerable to symlink attacks;
consider using \function{tmpfile()} instead.} consider using \function{tmpfile()} (section \ref{os-newstreams})
Availability: Macintosh, \UNIX, Windows. instead.} Availability: Macintosh, \UNIX, Windows.
\end{funcdesc} \end{funcdesc}
\begin{funcdesc}{tmpnam}{} \begin{funcdesc}{tmpnam}{}
...@@ -1113,12 +1113,13 @@ responsible for properly creating and managing files created using ...@@ -1113,12 +1113,13 @@ responsible for properly creating and managing files created using
paths returned by \function{tmpnam()}; no automatic cleanup is paths returned by \function{tmpnam()}; no automatic cleanup is
provided. provided.
\warning{Use of \function{tmpnam()} is vulnerable to symlink attacks; \warning{Use of \function{tmpnam()} is vulnerable to symlink attacks;
consider using \function{tmpfile()} instead.} consider using \function{tmpfile()} (section \ref{os-newstreams})
Availability: \UNIX, Windows. This function probably shouldn't be used instead.} Availability: \UNIX, Windows. This function probably
on Windows, though: Microsoft's implementation of \function{tmpnam()} shouldn't be used on Windows, though: Microsoft's implementation of
always creates a name in the root directory of the current drive, and \function{tmpnam()} always creates a name in the root directory of the
that's generally a poor location for a temp file (depending on current drive, and that's generally a poor location for a temp file
privileges, you may not even be able to open a file using this name). (depending on privileges, you may not even be able to open a file
using this name).
\end{funcdesc} \end{funcdesc}
\begin{datadesc}{TMP_MAX} \begin{datadesc}{TMP_MAX}
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment