Return-Path: <awaresystems.be+caf_=filtered=awaresystems.be@gmail.com>
Delivered-To: filtered@awaresystems.be
Received: from mx-c.one.com (mx-c.one.com [91.198.169.50])
	by mail6.local (Postfix) with ESMTP id 28B098014FAF4
	for <filtered@awaresystems.be>; Tue, 21 May 2013 16:17:02 +0200 (CEST)
X-Virus-Scanned: by one.com
Received-SPF: pass (mx-c: domain of awaresystems.be+caf_=filtered=awaresystems.be@gmail.com designates 209.85.215.41 as permitted sender)
X-Greylist: whitelisted by SQLgrey-1.8.0-rc2
Received: from mail-la0-f41.google.com (mail-la0-f41.google.com [209.85.215.41])
	by mx-c.one.com (Postfix) with ESMTP id B81F7A82EEB
	for <filtered@awaresystems.be>; Tue, 21 May 2013 14:17:01 +0000 (UTC)
Received: by mail-la0-f41.google.com with SMTP id ee20so745453lab.28
        for <filtered@awaresystems.be>; Tue, 21 May 2013 07:17:01 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=x-forwarded-to:x-forwarded-for:delivered-to:domainkey-status
         :x-gmail-fetch-info:delivered-to:x-virus-scanned:x-greylist:date
         :from:x-x-sender:to:in-reply-to:message-id:references:user-agent
         :mime-version:x-greylist:cc:subject:x-beenthere:x-mailman-version
         :precedence:list-id:list-unsubscribe:list-archive:list-post
         :list-help:list-subscribe:content-type:content-transfer-encoding
         :sender:errors-to;
        bh=d4LQ7j4hxem1MWDPm+NUMjy6Y5wAFeztYneDL+svsmI=;
        b=h4pDN2W6ukoTA6PYdD0P5l9UxTKaLvHdAV1nMNOQu2ihckbRbnmfLfFZ/749oRQIQ9
         Ycaan5x+Fr4KZrbcJtpcqjMs5ANLl84nqsOHjjh22nU1fm7rjZW9f2vIjxFfHqZImr6w
         kbm3aB3MtZEgu0DPHWG4fZwW9zEkom+0QL75BtKSjK78YGFDMKNLnwV707x5lpAghyFT
         EoXGM5s3Va6oDRtorSqF9uO20a2QIoaJcNw0zGJPxmkzCGc0wHUUP/dHQLWeUxe254gE
         tCXsXqL88MF5lOniRRO2oPi0nLskyVRa98/e566cYzWOze6zGkVVGXR7USTuYvPlUKA9
         xSWg==
X-Received: by 10.112.155.202 with SMTP id vy10mr1674016lbb.51.1369145821178;
        Tue, 21 May 2013 07:17:01 -0700 (PDT)
X-Forwarded-To: filtered@awaresystems.be
X-Forwarded-For: awaresystems.be@gmail.com filtered@awaresystems.be
Delivered-To: awaresystems.be@gmail.com
Received: by 10.114.29.36 with SMTP id g4csp131186ldh;
        Tue, 21 May 2013 07:17:00 -0700 (PDT)
X-Received: by 10.112.168.5 with SMTP id zs5mr1648789lbb.66.1369145819756;
        Tue, 21 May 2013 07:16:59 -0700 (PDT)
DomainKey-Status: bad format
Received-SPF: neutral (google.com: 195.47.247.149 is neither permitted nor denied by best guess record for domain of tiff-bounces@lists.maptools.org) client-ip=195.47.247.149;
Received: by 10.112.15.69 with POP3 id v5mf5354322lbc.19;
        Tue, 21 May 2013 07:16:59 -0700 (PDT)
X-Gmail-Fetch-Info: info@awaresystems.be 1 pop.awaresystems.be 110 info@awaresystems.be
Delivered-To: info@awaresystems.be
Received: from mx-x.one.com (mx-x.one.com [195.47.247.149])
	by mail6.local (Postfix) with ESMTP id E6E0B8014FAF5
	for <info@awaresystems.be>; Tue, 21 May 2013 16:14:12 +0200 (CEST)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0-rc2
Received: from lists.maptools.org (ks365428.kimsufi.com [94.23.4.142])
	by mx-x.one.com (Postfix) with ESMTP id 5456C26289
	for <info@awaresystems.be>; Tue, 21 May 2013 14:13:27 +0000 (UTC)
Received: from [10.1.0.241] (localhost.localdomain [127.0.0.1])
	by lists.maptools.org (Postfix) with ESMTP id 977CE35C029;
	Tue, 21 May 2013 09:13:29 -0500 (EST)
Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74])
	by lists.maptools.org (Postfix) with ESMTPS id B535735C025
	for <tiff@lists.maptools.org>; Tue, 21 May 2013 09:11:44 -0500 (EST)
Received: from freddy.simplesystems.org (freddy.simplesystems.org
	[65.66.246.65])
	by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id
	r4LEBeUZ004965; Tue, 21 May 2013 09:11:40 -0500 (CDT)
Date: Tue, 21 May 2013 09:11:40 -0500 (CDT)
From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
X-X-Sender: bfriesen@freddy.simplesystems.org
To: Chris Liddell <chris.liddell@artifex.com>
In-Reply-To: <CAGy8pWr-M3oAt34iPaFFpQTKwrbGrQxzt1NKZsQKRLD_c+fYiw@mail.gmail.com>
Message-ID: <alpine.GSO.2.01.1305210909030.2267@freddy.simplesystems.org>
References: <CAGy8pWr-M3oAt34iPaFFpQTKwrbGrQxzt1NKZsQKRLD_c+fYiw@mail.gmail.com>
User-Agent: Alpine 2.01 (GSO 1266 2009-07-14)
MIME-Version: 1.0
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2
	(blade.simplesystems.org [65.66.246.90]);
	Tue, 21 May 2013 09:11:40 -0500 (CDT)
Cc: tiff@lists.maptools.org
Subject: Re: [Tiff] memory management function calls
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TIFF and libtiff discussion <tiff.lists.maptools.org>
List-Unsubscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=unsubscribe>
List-Archive: <http://lists.maptools.org/mailman/private/tiff>
List-Post: <mailto:tiff@lists.maptools.org>
List-Help: <mailto:tiff-request@lists.maptools.org?subject=help>
List-Subscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org

On Tue, 21 May 2013, Chris Liddell wrote:

> 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?

I am not so sure about the extra "opaque pointer" bit, but having the 
ability to specify the memory allocation functions to use (as zlib and 
libpng do) would be useful.

A key issue is that the existing libtiff ABI can't be impacted by any 
such change.

Bob
-- 
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/
_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
