Received: from sgi.sgi.com (192.48.153.1) by cerious.com
 with SMTP (Apple Internet Mail Server 1.1.1); Wed, 22 Jan 1997 18:17:24 -0500
Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by sgi.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id PAA29863; Wed, 22 Jan 1997 15:08:21 -0800
Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id UAA02796 for tiff-list; Wed, 22 Jan 1997 20:04:17 GMT
Received: from sgi.sgi.com (sgi.engr.sgi.com [192.26.80.37]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id MAA02778 for <tiff-relay@relay.engr.sgi.com>; Wed, 22 Jan 1997 12:04:15 -0800
Received: from giraffe.asd.sgi.com (giraffe.asd.sgi.com [192.26.72.158]) by sgi.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id MAA14260 for <tiff@sgi.com>; Wed, 22 Jan 1997 12:04:14 -0800
Received: from melange.engr.sgi.com by giraffe.asd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1502/951211.SGI)
	 id MAA07360; Wed, 22 Jan 1997 12:04:13 -0800
Received: from localhost by melange.engr.sgi.com via SMTP (940816.SGI.8.6.9/950213.SGI.AUTOCF)
	 id MAA17869; Wed, 22 Jan 1997 12:04:12 -0800
Message-Id: <199701222004.MAA17869@melange.engr.sgi.com>
X-Mailer: exmh version 2.0alpha 12/3/96
To: tdn@eccentric.esd.sgi.com (Todd D. Newman)
cc: tiff@sgi.com
Subject: Re: Reading from standard in 
Reply-To: Sam Leffler <sam@relay.engr.SGI.COM>
In-reply-to: Your message of "Wed, 22 Jan 1997 10:31:37 PST."
             <199701221831.KAA06208@eccentric.esd.sgi.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 22 Jan 1997 12:04:09 -0800
From: Sam Leffler <sam@melange.engr.sgi.com>
Sender: owner-tiff@relay.engr.SGI.COM
Precedence: bulk
Status: R

    To:  tiff@sgi.com
    Subject:  Reading from standard in
    Date: Wed, 22 Jan 1997 10:31:37 PST
    From:  tdn@eccentric.esd.sgi.com (Todd D. Newman)

    This is probably a FAQ, but I don't see an answer anywhere. Is libtiff 
supposed
    to support standard in/standard out a la Unix?  If you look at 
TIFFClientOpen
    you'll see it doing strlen on the file name.  This doesn't work for a null
    file name. 
    
    My question is whether this is a bug or a feature. 
    
There is no direct support for reading/writing an i/o stream that does
not support random access.

        Sam


