Date: Tue, 20 Aug 2019 12:28:49 +0200 From: Ismael Luceno <ismael@...ev.co.uk> To: musl@...ts.openwall.com Subject: Re: [PATCH] Add copy_file_range system call On 19/Aug/2019 20:56, Rich Felker wrote: <...> > Is there a reason for the choice to put it in unistd.h? Similar > functions seem to have gone in fcntl.h. unistd.h does not make the > loff_t type available which could be problematic to callers using it, > since they really should (for API compatibility) be declaring the > objects whose addresses they pass as loff_t. > > If glibc does it here and exposes loff_t in unistd.h we might need to > consider doing that too with _GNU_SOURCE. +1. I've seen some code in the wild depend on loff_t.
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.