- 2013.09.03 15:33 "Re: [Tiff] memory management function calls", by Chris Liddell
2013.09.03 18:53 "Re: [Tiff] memory management function calls", by Frank Warmerdam
On Tue, Sep 3, 2013 at 8:33 AM, Chris Liddell <chris.liddell@artifex.com>wrote:
On 02/08/13 09:04, 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!
Deafening silence continues........
Chris,
I haven't replied because I don't see much need for this. The only situation I have seen where something like this might be useful is the Postgresql pool allocator where once a transaction is complete all allocations related to it are force-freed.
I'm not keen on the change, but I'm not necessarily fighting it.
Best regards,
Frank
-- ---------------------------------------+-------------------------------------- I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | Geospatial Software Developer