AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2013.11.05 16:20 "Re: [Tiff] memory management function calls", by Lee Howard
2013.11.05 13:28 "Re: [Tiff] memory management function calls", by Bruce A. Mallett
2013.11.05 15:41 "Re: [Tiff] memory management function calls", by Chris Liddell
2013.11.06 05:10 "Re: [Tiff] memory management function calls", by Bruce A. Mallett

2013.11.05 13:28 "Re: [Tiff] memory management function calls", by Bruce A. Mallett

Very opportune: I'm just finding this thread as the result of a search (after having received an assignment to update from 3.8.x to a later libtiff). A project I am on uses libtiff in an embedded system containing multiple components. These components have different allocators so over the years similar modifications to libtiff have been made locally to provide a way for each component can pass in its own allocator (and deallocator, etc). The fact that your mod. provides for passing a memory context aligns well will our main use case: one of our allocators requires context info so that it can be told about the expected use & duration of the object to be allocated as well as a suggested pool to use.

Having our own set of local changes complicates updating to a newer release, it would be very beneficial to us if this kind of capability were baked into the distribution.

              - Bruce

On 08/02/2013 04:04 AM, Chris Liddell wrote: > On 25/06/13 12:12, Chris Liddell wrote:

>> So, as I said, I took a punt at these changes (sorry for the delay - >> other projects etc....).

>>
>> I created a browsable git repo here:
>>
>> http://git.ghostscript.com/?p=user/chrisl/libtiff.git;a=summary
>>
>> You can take a look at the diff there.
>>

>> I don't *think* I've changed the existing ABI, where such would be >> required, I've added a new API call.

>>

>> Comments, questions, criticisms, general rants all (somewhat) welcome... > So, not much love (or otherwise) on this?

>
> Not even a complaint about putting up the patch in an unfavoured form?
>
>

> I'd expected to be berated for something by now!

>
> Chris
>