diff options
| author | Neal Norwitz <nnorwitz@gmail.com> | 2006-02-05 05:45:43 (GMT) |
|---|---|---|
| committer | Neal Norwitz <nnorwitz@gmail.com> | 2006-02-05 05:45:43 (GMT) |
| commit | 0e6bc8c260f640ceee515e9873353778472e0a00 (patch) | |
| tree | f567d2bbbde27ae16288e1e94edc4ff0acf13441 /Doc/lib/libmmap.tex | |
| parent | d1cfc8ade1f661f02286f2b81123d4d436c6d9d0 (diff) | |
| download | cpython-0e6bc8c260f640ceee515e9873353778472e0a00.zip cpython-0e6bc8c260f640ceee515e9873353778472e0a00.tar.gz cpython-0e6bc8c260f640ceee515e9873353778472e0a00.tar.bz2 | |
Patch #1407135, bug #1424041, make mmap.mmap(-1, length) work the same
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.
Diffstat (limited to 'Doc/lib/libmmap.tex')
| -rw-r--r-- | Doc/lib/libmmap.tex | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/Doc/lib/libmmap.tex b/Doc/lib/libmmap.tex index e7db814..3dca40f 100644 --- a/Doc/lib/libmmap.tex +++ b/Doc/lib/libmmap.tex @@ -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 |