Hi Scott. pdf_fsys_file_get_size(...) pdf_fsys_file_set_size(...) pdf_fsys_file_set_pos(...) pdf_fsys_file_get_pos(...)
all convey size information with pdf_size_t. size_t will be 32-bits on some systems (4GB size limit) I regularly work with 1GB PDF files - 4GB can't be far off... Shouldn't we convey all file size information (offsets and sizes) with pdf_i64_t on all systems? (I.e. shouldn't we handle these offsets/sizes as pdf_i64_t instead of pdf_size_t?) The Adobe SDK manages this problem by providing a set of 64-bit specific functions in platforms supporting it. Instead we are following a simpler strategy: we assume that the people wanting to manipulate 4GB PDF files will be working in a 64 bits architecture. If you think that strategy to be unreasonable, please say so: it is better to manage this kind of issues in an early stage :) -- Jose E. Marchesi [email protected] GNU Project http://www.gnu.org
