Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!icdoc!dbh
From: dbh@doc.ic.ac.uk (Denis Howe)
Newsgroups: comp.sys.acorn
Subject: Re: Pseudo Filing Systems via *set
Message-ID: <DBH.91May6122307@asun4.doc.ic.ac.uk>
Date: 6 May 91 11:23:06 GMT
References: <1991May1.184943.1835@ugle.unit.no> <6815@acorn.co.uk>
Organization: Dept. of Computing, Imperial College, London, UK
Lines: 18
In-Reply-To: osmith@acorn.co.uk's message of 2 May 91 16:07:20 GMT

In article <6815@acorn.co.uk> osmith@acorn.co.uk (Owen Smith) writes:
>Try *set foo$dir adfs::4.$.fred
>    *setmacro foo$path <foo$dir>.,adfs::4.$.fred2.
>
>Now, when you try to read a file eg. *dump foo:wombat, all of the directories
>on the path variable foo$path will be searched.

Someone reported a problem with using macros as path variables due to
a bug in OS_ReadVarVal which tries to expand macros into a
non-existent buffer.

foo$path only needs to be a macro if you want it to reflect subsequent
changes to <foo$dir> so you could use probably plain *Set here, no?

--
Denis Howe <dbh@doc.ic.ac.uk>      C-C
H558A Imperial College London     C-C-C
   +44 (71) 589 5111 x5064         N=N