🚀 go-pugleaf

In article <1127@apple.UUCP> dwb@apple.UUCP (David W. Berry) 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?
|-- 
|	David W. Berry
|	dwb@well.uucp                   dwb@Delphi
|	dwb@apple.com                   293-0752@408.MaBell

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?
  Larry at Apple recently posted some code that helps with this, and it is
muchly appreciated.  Thanks Larry.  Do you read Badger?

					Reid
					+=--