rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Scott Merrilees <Sm@cerberus.bhpese.oz.au>
To: rc@archone.tamu.edu (The rc Mailing List)
Subject: Re: path caching
Date: Sun, 9 Feb 1992 08:15:47 -0600	[thread overview]
Message-ID: <199202090315.AA27658@cerberus.bhpese.oz.au> (raw)
In-Reply-To: <9202081331.AA07997@skinner.cs.wisc.edu>; from "DaviD W. Sanderson" at Feb 8, 92 7:31 am

> 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


  reply	other threads:[~1992-02-09  3:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-02-08 13:31 DaviD W. Sanderson
1992-02-09 14:15 ` Scott Merrilees [this message]
1992-02-08 22:01 Scott Merrilees
1992-02-08 14:32 ` John Mackin
1992-02-08 17:19 ` Chris Siebenmann
1992-02-09 14:06   ` Scott Merrilees
1992-02-09 18:55 ` Matthew Farwell
1992-02-10 13:34   ` Scott Merrilees
1992-02-12 17:32     ` Matthew Farwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199202090315.AA27658@cerberus.bhpese.oz.au \
    --to=sm@cerberus.bhpese.oz.au \
    --cc=rc@archone.tamu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).