Cliff Woolley wrote:
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?
Which dup() do you mean: the dup(2) or the naming convention of using "_dup*()" for this family of apr_file_t functions?
--Brian
