Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #14686

Re: Auto-update program cache feature

From Eduardo Bustamante <dualbus@gmail.com>
Newsgroups gnu.bash.bug
Subject Re: Auto-update program cache feature
Date 2018-10-04 05:10 -0700
Message-ID <mailman.1700.1538655029.1284.bug-bash@gnu.org> (permalink)
References <CAH8yC8kgkFRBaq85Z-tf+4x+DNqEU1CD-iZMgzJ6nYge-N4Sgg@mail.gmail.com> <20181004013022.GA28424@ubuntu> <CAH8yC8mR1tiAUmqN=jVm5ZX2wuRKL6evu0kHVa=+90t-WfUGQQ@mail.gmail.com>

Show all headers | View raw


On Wed, Oct 3, 2018 at 11:20 PM Jeffrey Walton <noloader@gmail.com> wrote:
(...)
> How Bash achieves it is an implementation detail left to the experts.
> I made a few suggestions that don't seem to fit well. That's OK
> because Bash internals is not my area of expertise.

I think it's important to always consider the cost (in terms of
implementation complexity and maintenance) of a feature we request
from a free software program :)

> Architecturally each instance of Bash is an object could receive a
> "clear cache" message. How it is achieved does not matter to me. What
> is important is, the right thing is done to relieve users from the
> extra work for the common case.

This paragraph contradicts what you said earlier. You keep suggesting
that Bash should adopt this global message passing system where every
instance of the shell can broadcast messages to each other... that is
EXTREMELY complicated.

Anyways, I should've read the manual before replying to this email
thread. There's already a mechanism in place for what you want, it's
the `checkhash' shopt.

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread


Thread

Re: Auto-update program cache feature Eduardo Bustamante <dualbus@gmail.com> - 2018-10-04 05:10 -0700

csiph-web