Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!im4u!rutgers!sri-spam!mordor!lll-lcc!pyramid!voder!apple!dwb
From: dwb@apple.UUCP (Dave W. Berry)
Newsgroups: comp.sys.mac
Subject: Re: obtaining the full pathname of a file
Message-ID: <1222@apple.UUCP>
Date: Tue, 30-Jun-87 15:24:00 EDT
Article-I.D.: apple.1222
Posted: Tue Jun 30 15:24:00 1987
Date-Received: Thu, 2-Jul-87 01:49:23 EDT
References: <1345@batcomputer.tn.cornell.edu> <1007@apple.UUCP>
Reply-To: dwb@apple.UUCP (Dave W. Berry)
Organization: Apple Computer Inc., Cupertino, USA
Lines: 21
Keywords: path restrict user

In article <684@unicus.UUCP> rae@unicus.UUCP (Clith de T'nir a.k.a. Reid Ellis) writes:
>In article <1127@apple.UUCP> dwb@apple.UUCP (David W. Berry) (me!) writes:
>|In article <665@unicus.UUCP> I write:
>|>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? :-)
>|	... And the correct thing to do
>|	is for the compiler to implement search paths so you don't
>|	have to give long full path names.  What happens if you
>|	rename the disk, or copy the whole structure to hard disk?
>I would agree that one should not *force* a user to use full pathnames,
>lest their fingers go numb :-), but what do you do when the user *does*
>type a long path?  I wouldn't want to restrict her from doing so, so I must
>support it in my application.  So my original point stands, What do you
>do to support long path names?
	If you just pass the full path name to the open call you don't
	need to do anything special.
-- 
	David W. Berry
	dwb@well.uucp                   dwb@Delphi
	dwb@apple.com                   293-0752@408.MaBell