Return-Path: <tiff-bounces@lists.maptools.org>
Received: from mailgate007.isp.belgacom.be (mailgate007.isp.belgacom.be [195.238.5.213])
        by inmx009.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-2.32) with ESMTP id l5TFSktD028137
        for <joris.at.lebbeke@skynet.be>; Fri, 29 Jun 2007 17:28:46 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from r153.dmsolutions.ca (HELO duke.maptools.org) ([209.217.116.153])
  by in.mx.skynet.be with ESMTP; 29 Jun 2007 17:28:45 +0200
Received: from duke.maptools.org (duke.maptools.org [127.0.0.1])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id l5TFHYbl001571;
	Fri, 29 Jun 2007 11:17:45 -0400
Received: from scooby.simplesystems.org (scooby.simplesystems.org
	[65.66.246.67])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id l5TFHWve001568
	for <tiff@lists.maptools.org>; Fri, 29 Jun 2007 11:17:32 -0400
Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74])
	by scooby.simplesystems.org (8.12.10+Sun/8.12.10) with ESMTP id
	l5TFHNW7022953; Fri, 29 Jun 2007 10:17:23 -0500 (CDT)
Date: Fri, 29 Jun 2007 10:17:23 -0500 (CDT)
From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
X-X-Sender: bfriesen@blade.simplesystems.org
To: Kevin Myers <kmyers1@clearwire.net>
Subject: Re: [Tiff] Suggested Source Changes for Building libtiff Under Windows
In-Reply-To: <10cd01c7ba3d$388bdcd0$bd14d9a6@gateway>
Message-ID: <Pine.SOC.4.60.0706291015260.922@blade.simplesystems.org>
References: <10cd01c7ba3d$388bdcd0$bd14d9a6@gateway>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: tiff@lists.maptools.org
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.4
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>
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org
X-UIDL: 000000000023ceae.000024be
X-MSP-STORE: Fri, 29 Jun 2007 17:28:54 +0200
Status: RO

On Fri, 29 Jun 2007, Kevin Myers wrote:
>
> 8. Add a port.h header file for modules located in the port subdirectory.
>
> Since configuration level handling of header files are already 
> required for any module that makes use of a function that may be 
> compiled under the port directory, it might make sense to consider 
> adding a port.h header file, and putting logic in the individual 
> files that reference these functions to reference port.h rather than 
> the corresponding standard header file when appropriate.  Might be 
> cleaner than using the currently implemented external function 
> reference approach.  Just something to consider...

I noticed this deficiency.  It is certainly valuable to supply a 
port.h header file which offers the needed prototypes.  In fact, the 
code may misbehave without it.

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/
