apr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jor...@apache.org
Subject svn commit: r493799 - /apr/apr/trunk/file_io/unix/readwrite.c
Date Sun, 07 Jan 2007 18:35:51 GMT
Author: jorton
Date: Sun Jan  7 10:35:50 2007
New Revision: 493799

URL: http://svn.apache.org/viewvc?view=rev&rev=493799
Log:
* file_io/unix/readwrite.c (apr_file_writev): Fix variable type and
spelling in comment.

Modified:
    apr/apr/trunk/file_io/unix/readwrite.c

Modified: apr/apr/trunk/file_io/unix/readwrite.c
URL: http://svn.apache.org/viewvc/apr/apr/trunk/file_io/unix/readwrite.c?view=diff&rev=493799&r1=493798&r2=493799
==============================================================================
--- apr/apr/trunk/file_io/unix/readwrite.c (original)
+++ apr/apr/trunk/file_io/unix/readwrite.c Sun Jan  7 10:35:50 2007
@@ -240,7 +240,7 @@
                                           apr_size_t nvec, apr_size_t *nbytes)
 {
 #ifdef HAVE_WRITEV
-    int bytes;
+    apr_ssize_t bytes;
 
     if ((bytes = writev(thefile->filedes, vec, nvec)) < 0) {
         *nbytes = 0;
@@ -253,8 +253,8 @@
 #else
     /**
      * The problem with trying to output the entire iovec is that we cannot
-     * maintain the behavoir that a real writev would have.  If we iterate
-     * over the iovec one at a time, we loose the atomic properties of 
+     * maintain the behaviour that a real writev would have.  If we iterate
+     * over the iovec one at a time, we lose the atomic properties of 
      * writev().  The other option is to combine the entire iovec into one
      * buffer that we could then send in one call to write().  This is not 
      * reasonable since we do not know how much data an iovec could contain.



Mime
View raw message