AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2013.05.21 10:32 "[Tiff] memory management function calls", by Chris Liddell
2013.05.21 14:11 "Re: [Tiff] memory management function calls", by Bob Friesenhahn
2013.05.21 15:11 "Re: [Tiff] memory management function calls", by Chris Liddell
2013.05.21 15:18 "Re: [Tiff] memory management function calls", by Bob Friesenhahn
2013.05.21 15:32 "Re: [Tiff] memory management function calls", by Chris Liddell
2013.05.21 15:38 "Re: [Tiff] memory management function calls", by Bob Friesenhahn
2013.05.21 17:21 "Re: [Tiff] memory management function calls", by Joris Van Damme
2013.05.21 17:28 "Re: [Tiff] memory management function calls", by Chris Liddell

2013.05.21 10:32 "[Tiff] memory management function calls", by Chris Liddell

Hello,

I'm a developer working on Ghostscript, and we use libtiff for our TIFF output "devices".

As a matter policy (primarily for easy porting), it's our policy that, wherever possible, libraries we include should be integrated in such a way that they work through Ghostcript's I/O and memory management functions.

I made changes to how we interface with libtiff a while back so the file I/O functions work that way, but looking at the memory management functions, there is no way this can currently be done, due to memory management functions always being called directly (rather than via function pointers, like the file I/O calls), and also there is no "context" passed into the memory functions.

If I were to make changes that would augment the libtiff API to allow an opaque pointer to "user data" to be passed into the memory functions, and changed the memory functions to be called through function pointers like the file I/O ones, would that be something of interest, and likely to be adopted?

Thanks,

Chris