summaryrefslogtreecommitdiff
path: root/file_io
diff options
context:
space:
mode:
authorwrowe <wrowe@13f79535-47bb-0310-9956-ffa450edef68>2002-06-03 19:25:34 +0000
committerwrowe <wrowe@13f79535-47bb-0310-9956-ffa450edef68>2002-06-03 19:25:34 +0000
commit700b8ed349c9aed7c8ed95e32a0b58f7c3e00098 (patch)
tree342b930656ad19f96d0541ff40c393a93c418d31 /file_io
parentcab48db5ef5bcd6cb2a25cd0574f113ff3ba8056 (diff)
downloadlibapr-700b8ed349c9aed7c8ed95e32a0b58f7c3e00098.tar.gz
Needs research and a decision
git-svn-id: http://svn.apache.org/repos/asf/apr/apr/trunk@63459 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'file_io')
-rw-r--r--file_io/win32/open.c11
1 files changed, 9 insertions, 2 deletions
diff --git a/file_io/win32/open.c b/file_io/win32/open.c
index 6435aa133..2ec0ee727 100644
--- a/file_io/win32/open.c
+++ b/file_io/win32/open.c
@@ -518,8 +518,15 @@ APR_DECLARE(apr_status_t) apr_os_file_put(apr_file_t **file,
(*file)->pool = pool;
(*file)->filehand = *thefile;
(*file)->ungetchar = -1; /* no char avail */
- (*file)->flags;
- (*file)->pipe;
+
+ /* XXX... we pcalloc above so these are zeroed. Is zero really
+ * the right answer when we passed flags into os_file_put?
+ * Should we be testing if thefile is a handle to a PIPE and
+ * set up the mechanics appropriately?
+ *
+ * (*file)->flags;
+ * (*file)->pipe;
+ */
return APR_SUCCESS;
}