apr_off_t warnings in win32

Dang... tossed the note, yet I wanted to reply to it.

Regarding the mismatch of integer sizes with some apr_off_t stuff (the 64
bit versus whatever): the correct change is to fix up the API to take an
apr_off_t as appropriate. The FS *does* need to accept documents that are
larger than 4G.

Of course, then we run into the issue of how to get that in/out of the FS in
chunks. Memory limits (apr_size_t) play a role in limiting some of the
interactions with the FS.

Basically, the strings table lengths are apr_off_t.

[ just commenting; I haven't really looked at this stuff, as it holds a
  lower priority than most of the other work... (although, conceivably, we
  may need to get the APIs and things cleaned up before 1.0) ]

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org