From f595e889b91a674eb94db7ca4d832da54f5194cd Mon Sep 17 00:00:00 2001
From: Tor Andersson <tor.andersson@artifex.com>
Date: Thu, 17 Aug 2017 15:01:09 +0200
Subject: Use int64_t for public file API offsets.

Don't mess with conditional compilation with LARGEFILE -- always expose
64-bit file offsets in our public API.
---
 docs/coding-style.html | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

(limited to 'docs')

diff --git a/docs/coding-style.html b/docs/coding-style.html
index d9a1602d..66eefd39 100644
--- a/docs/coding-style.html
+++ b/docs/coding-style.html
@@ -83,9 +83,7 @@ In general:
 <li> array sizes, string lengths, and allocations are measured using size_t.
 	size_t is 32bit in 32bit builds, and 64bit on all 64bit builds.
 <li> buffers of data use unsigned chars (or uint8_t).
-<li> Offsets within files/streams are represented using fz_off_t.
-	fz_off_t is 64bits in 64bit builds, or in 32bit builds with FZ_LARGEFILE defined.
-	Otherwise it is a native int (so 32bit in 32bit builds).
+<li> Offsets within files/streams are represented using int64_t.
 </ul>
 
 <p>
-- 
cgit v1.2.3