mirror of
https://github.com/python/cpython.git
synced 2025-08-04 08:59:19 +00:00
on both Unix (SVR4 and BSD) and Windows. Restores behaviour of passing -1 for anonymous memory on Unix. Use MAP_ANONYMOUS instead of _ANON since the latter is deprecated according to Linux (gentoo) man pages. Should we continue to allow mmap.mmap(0, length) to work on Windows? 0 is a valid fd. Will backport bugfix portions.
This commit is contained in:
parent
d1cfc8ade1
commit
0e6bc8c260
5 changed files with 68 additions and 13 deletions
|
@ -37,7 +37,8 @@ taken from the specified file. Assignment to an
|
|||
exception. Assignment to an \constant{ACCESS_WRITE} memory map
|
||||
affects both memory and the underlying file. Assignment to an
|
||||
\constant{ACCESS_COPY} memory map affects memory but does not update
|
||||
the underlying file.
|
||||
the underlying file. \versionchanged[To map anonymous memory,
|
||||
-1 should be passed as the fileno along with the length]{2.5}
|
||||
|
||||
\begin{funcdesc}{mmap}{fileno, length\optional{, tagname\optional{, access}}}
|
||||
\strong{(Windows version)} Maps \var{length} bytes from the file
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue