On 29 April 2016 at 18:25, Random832
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 off_in is not NULL, then off_in must point to a buffer that specifies the starting offset where bytes from fd_in will be read. The file offset of fd_in is not changed, >>>but off_in 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()?