[Python-Dev] Convert int() to size_t in Python/C (original) (raw)
Martin Panter vadmium+py at gmail.com
Fri Apr 29 19:26:53 EDT 2016
- Previous message (by thread): [Python-Dev] Convert int() to size_t in Python/C
- Next message (by thread): [Python-Dev] Convert int() to size_t in Python/C
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 29 April 2016 at 18:25, Random832 <random832 at fastmail.com> wrote:
On Fri, Apr 29, 2016, at 14:11, Marcos Dione wrote:
These are not output parameters, even if they're pointers. they'r using the NULL pointer to signal that the current offsets should not be touched, to differentiate from a offset of 0. Something that in Python we would use None. That's not actually true according to the documentation. (And if it were, they could simply use -1 rather than a null pointer) . . . * If offin is not NULL, then offin must point to a buffer that specifies the starting offset where bytes from fdin will be read. The file offset of fdin is not changed, >>>but offin is adjusted appropriately.<<<
Linux’s sendfile() syscall takes a similar offset parameter that may be updated, but Python’s os.sendfile() wrapper does not return the updated offset. Do you think we need to return the updated offsets for copy_file_range()?
- Previous message (by thread): [Python-Dev] Convert int() to size_t in Python/C
- Next message (by thread): [Python-Dev] Convert int() to size_t in Python/C
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]