Path: utzoo!mnetor!uunet!husc6!ncar!ames!lll-lcc!well!aleks
From: aleks@well.UUCP (Brian J. Witt)
Newsgroups: comp.sys.amiga
Subject: Re: The 1001 Paths
Message-ID: <5489@well.UUCP>
Date: 20 Mar 88 23:31:06 GMT
References: <4587@garfield.UUCP>
Reply-To: aleks@well.UUCP (Brian J. Witt)
Organization: Whole Earth 'Lectronic Link, Sausalito, CA
Lines: 27
Keywords: open

on't believe in line eaters]

Bear with my first posting..


In article <4587@garfield.UUCP> john13@garfield.UUCP (John Russell) writes:
>Seems to me like the "set" command is the ideal way to deal with the idea
>of multiple possible paths to any particular file. Manx supplies one with
>their compiler, and ARP contains a (much, much smaller) freely redistributable
>set command which is compatible with the Manx format.
>
>set FONTS=fonts:!fontdisk1:fonts/!wb:fonts/!dpaint:fonts/
>
>and write a little parse routine to search all locations for any given file.
>This isn't system-wide, but can certainly be added to new and old applications
>alike. To the fellow that wanted include files searched for this way, this is
>just the method that Manx uses. Of course it's up to the application to
>support it, but then an "include file" is specific to a certain type of
>application.
>

  What you need to do is write Open() so it understands these pathnames!
  That way it is transparent to all applications...  Just think of all
  those linked directories you could search!  You must however, put
  in some rule about when an off-line volume is encountered.
 
"I got my opinions from a shoebox that spoke to me.."