On Sat, 29 Jun 2002, Brian Pane wrote: > This patch adds an apr_file_setaside() function that moves > an apr_file_t from one pool to another without doing any > dup(2) or mmap(2) operations.
Why not keep the dup() and add in a "transfer ownership" feature like the mmap dup uses? After all, the whole reason we added an apr_mmap_dup() was to allow the apr_mmap_t to be moved from one pool to another. It would be mildly annoying to have the mmap and file code diverge again... --cliff
