On Wed, 21 May 2008, Dan Fandrich wrote:

> What about this scenario: libcurl is built without LFS, and the app is built
> with. The library will then be expecting a long while the app will be
> providing a long long. The naive approach of checking sizeof(off_t) in the
> header file will fail in this case. I can't think of how to do the right
> thing in this case without either a run-time size check or encoding the
> actual size expected in a curl header file.

Yeah, we're back to square one I'd say.

And out of the two choices, I prefer encoding the expected size into the
header file, since that way we should be able to avoid touching the actual ABI
or API.

-- 
  / daniel.haxx.se