Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site unicus.UUCP
Path: utzoo!mnetor!yetti!unicus!rae
From: rae@unicus.UUCP (Clith de T'nir a.k.a. Reid Ellis)
Newsgroups: comp.sys.mac
Subject: Re: obtaining the full pathname of a file
Message-ID: <665@unicus.UUCP>
Date: Fri, 19-Jun-87 17:59:18 EDT
Article-I.D.: unicus.665
Posted: Fri Jun 19 17:59:18 1987
Date-Received: Sat, 20-Jun-87 20:21:09 EDT
References: <1345@batcomputer.tn.cornell.edu> <1007@apple.UUCP> <204@drilex.UUCP> <19339@ucbvax.BERKELEY.EDU> <6462@dartvax.UUCP>
Reply-To: rae@unicus.UUCP (Clith de T'nir a.k.a. Reid Ellis)
Organization: Unicus Software Inc.
Lines: 21
Keywords: path

In article <6462@dartvax.UUCP> earleh@dartvax.UUCP writes:
|
| ... Byte the bullet, programmers!  Use PBOpen, PBRead, PBWrite, and
| the entire ensemble of IN ROM Macintosh file handling routines ...
| ... you don't have to 
| obtain the pathname of the file, and you don't have to worry about what
| happens to your file connection when a disk gets ejected.  Of course,
| this reduces "portability" but who are we kidding here?

Um, doesn't this ignore applications where a path is read from a text
file? [along the lines of a C compiler's "#include <a:long:path>"]  What
then?  Make the user memorize vRefNums of his folders? :-)

							Reid
							+=--
---
					"ZOT, YOU JERK!"
						- Jenny
Reid Ellis, aka Clith de T'nir
		{seismo!mnetor, utzoo!yetti}!unicus!rae	(uucp)
		mnetor!unicus!rae@seismo.css.gov	(arpa)