aboutsummaryrefslogtreecommitdiff
path: root/lib/README.curl_off_t
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2008-08-26 12:57:29 +0000
committerDaniel Stenberg <daniel@haxx.se>2008-08-26 12:57:29 +0000
commit132cd3aa2c91e32b08e31d6be38534933245bd68 (patch)
tree4e439dbab7efb2be69d13e9a0968b47b8bc227f2 /lib/README.curl_off_t
parentfef60d9d4155c75809b278968cff345cc47be512 (diff)
spell out some benefits of this new approach of doing curl_off_t
Diffstat (limited to 'lib/README.curl_off_t')
-rw-r--r--lib/README.curl_off_t13
1 files changed, 13 insertions, 0 deletions
diff --git a/lib/README.curl_off_t b/lib/README.curl_off_t
index b60179da0..8e440a26c 100644
--- a/lib/README.curl_off_t
+++ b/lib/README.curl_off_t
@@ -27,6 +27,19 @@ In both these cases, the curl_off_t type will now (after the transition) be
64bit where it previously were 32bit. This will cause a binary incompatibility
that you MAY need to deal with.
+Benefits
+--------
+
+This new way has several benefits:
+
+o Platforms without LFS support can still use libcurl to do >32 bit file
+ transfers and range operations etc as long as they have >32 bit datatypes
+ supported.
+
+o Applications will no longer easily build with the curl_off_t size
+ mismatched, which has been a very frequent (and annoying) problem with
+ libcurl <= 7.18.2
+
Historicly
----------