Charles-François Natali <neolo...@free.fr> added the comment: > What's wrong with mmap? It uses list of optional arguments (`flags`, > `prot`, `access`) and not only one `flags` argument.
Of course it does, as the mmap syscall(), since this arguments have nothing to do with one another. I was refering to your proposal of splitting sendfile's `flags` argument, which is currently a bitmask, into distinct arguments (diskio=True, wait=True, sync=False). If we did this for, let's say, mmap() `flags`, this would end up in a bazillion optional arguments, because there a re so many possible values for `flags` (MAP_SHARED, MAP_PRIVATE, MAP_ANONYMOUS, MAP_DENYWRITE...). Bitmasks are a clear and compact way to pass optional arguments, and should be kept. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15078> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
