Return-Path: <awaresystems.be+caf_=filtered=awaresystems.be@gmail.com>
Delivered-To: filtered@awaresystems.be
Received: from mx-s.one.com (mx-s.one.com [91.198.169.250])
	by mail6.b-one.net (Postfix) with ESMTP id 9C07580185277
	for <filtered@awaresystems.be>; Mon, 30 Jul 2012 15:06:04 +0200 (CEST)
X-Virus-Scanned: by one.com
Received-SPF: pass (mx-s: domain of awaresystems.be+caf_=filtered=awaresystems.be@gmail.com designates 209.85.220.176 as permitted sender)
X-Greylist: whitelisted by SQLgrey-1.8.0-rc2
Received: from mail-vc0-f176.google.com (mail-vc0-f176.google.com [209.85.220.176])
	by mx-s.one.com (Postfix) with ESMTP id 402FDE2A9D9
	for <filtered@awaresystems.be>; Mon, 30 Jul 2012 13:06:04 +0000 (UTC)
Received: by vcbfl11 with SMTP id fl11so5797528vcb.21
        for <filtered@awaresystems.be>; Mon, 30 Jul 2012 06:06:03 -0700 (PDT)
Received: by 10.52.94.36 with SMTP id cz4mr9762464vdb.10.1343653563401;
        Mon, 30 Jul 2012 06:06:03 -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.58.208.231 with SMTP id mh7csp28622vec;
        Mon, 30 Jul 2012 06:06:03 -0700 (PDT)
Received: by 10.220.221.131 with SMTP id ic3mr10894264vcb.46.1343653560781;
        Mon, 30 Jul 2012 06:06:00 -0700 (PDT)
Received-SPF: neutral (google.com: 91.198.169.248 is neither permitted nor denied by best guess record for domain of tiff-bounces@lists.maptools.org) client-ip=91.198.169.248;
Received: by 10.230.67.1 with POP3 id p1mf3256611vbi.13;
        Mon, 30 Jul 2012 06:06:00 -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-q.one.com (mx-q.one.com [91.198.169.248])
	by mail6.b-one.net (Postfix) with ESMTP id DE66880185275
	for <info@awaresystems.be>; Mon, 30 Jul 2012 15:03:05 +0200 (CEST)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0-rc2
Received: from lists.maptools.org (lists.maptools.org [65.39.174.144])
	by mx-q.one.com (Postfix) with ESMTP id 67D7662280C
	for <info@awaresystems.be>; Mon, 30 Jul 2012 13:03:05 +0000 (UTC)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by lists.maptools.org (Postfix) with ESMTP id 5D5223AD9CE;
	Mon, 30 Jul 2012 08:01:34 -0500 (EST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154])
	by lists.maptools.org (Postfix) with ESMTPS id 449E11EDB5F
	for <tiff@lists.maptools.org>; Mon, 30 Jul 2012 07:40:33 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by mailb2.tigertech.net (Postfix) with ESMTP id B8E181C0E15;
	Mon, 30 Jul 2012 05:40:31 -0700 (PDT)
Received: from [10.5.0.86] (unknown [38.124.250.3])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mailb2.tigertech.net (Postfix) with ESMTPSA id 650721C0930;
	Mon, 30 Jul 2012 05:40:31 -0700 (PDT)
Message-ID: <501680BE.9060608@ql.org>
Date: Mon, 30 Jul 2012 08:40:30 -0400
From: Jay Berkenbilt <ejb@ql.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: tiff@lists.maptools.org
References: <26455.1343591491@sss.pgh.pa.us>
In-Reply-To: <26455.1343591491@sss.pgh.pa.us>
Subject: Re: [Tiff] What about hiding not-officially-exported functions?
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 07/29/2012 03:51 PM, Tom Lane wrote:
> When we had the discussion of symbol versioning back in January,
> I had the idea that part of what was being discussed was deleting all
> not-officially-exported functions from the library's symbol table,
> so it would be impossible not just deprecated for client applications
> to call them.  I noticed by accident that this is not in fact what was
> done: libtiff.map and libtiffxx.map still allow all function names to
> get through to the finished library.  There might be a filter in
> effect when building on Windows; I'm not sure what the libtiff.def
> file is used for, but it looks like it might be intended for Windows.
> Nothing of the sort happens on Linux though.
>
> Is it intentional that we're still letting clients call things like,
> say, _TIFFsetDoubleArray()?  If not, at what point could we consider
> changing it?  It's probably too late for 4.0, at least on distros
> that have already shipped that.  I still have a bit of a window to
> apply a filter for Red Hat's distribution of 4.0, though.
>
> 			regards, tom lane
>
Debian hasn't fully transitioned either, though tiff 4 is available.  If
previously exported symbols disappear from the interface, that requires
an soname bump, so we would have to go to libtiff.so.6.  The transition
in debian to make tiff 4 the default won't occur until after Wheezy is
released.

--Jay
_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
