From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from munnari.oz.au ([128.250.1.21]) by archone.tamu.edu with SMTP id <45332>; Sat, 8 Feb 1992 21:18:48 -0600 Received: from cerberus.bhpese.oz (via metro) by munnari.oz.au with SunIII (5.64+1.3.1+0.50) id AA17474; Sun, 9 Feb 1992 14:17:42 +1100 (from Sm@cerberus.bhpese.oz.au) Received: from localhost by cerberus.bhpese.oz.au with ELM 2.3 PL5 id AA27658; Sun, 9 Feb 1992 14:15:48 +1100; sendmail 5.65c/Sm3.0RMSU (from Sm@cerberus.bhpese.oz.au for rc@archone.tamu.edu@munnari.oz.au) Message-Id: <199202090315.AA27658@cerberus.bhpese.oz.au> From: Scott Merrilees Subject: Re: path caching To: rc@archone.tamu.edu (The rc Mailing List) Date: Sun, 9 Feb 1992 08:15:47 -0600 In-Reply-To: <9202081331.AA07997@skinner.cs.wisc.edu>; from "DaviD W. Sanderson" at Feb 8, 92 7:31 am X-Face: '82~l%BnDBWVn])DV^cl_%bla$T]kNbRN&]>v{ED9[" DaviD W. Sanderson (dws@cs.wisc.edu) > Since your scheme relies on symbolic links, it won't work on many > systems. Something I am prepared to wear, as the machines I mostly want to use do have symlinks. > If you want a cache, then I think a purely memory-based cache would be > better. This is neither persistant, sharable nor externally user manipulable. > Simply arrange to clear the cache when $path is assigned to. > No new variables, no new builtins required. Then I have to modify both the path lookup code & the variable lookup code. I didn't want the rest of the shell to know about it. Anyway, it will be more interesting when I have some data from the trial I am running. Sm -- Scott Merrilees, BHP Information Technology, Newcastle, Australia Internet: Sm@bhpese.oz.au Phone: +61 49 40 2132 Fax: ... 2165