zsh-workers
 help / color / mirror / code / Atom feed
From: Clint Adams <clint@zsh.org>
To: zsh-workers@sunsite.dk
Subject: Re: autoloading from deleted wordcode digest files
Date: Wed, 6 Jun 2001 10:25:57 -0400	[thread overview]
Message-ID: <20010606102557.B23921@dman.com> (raw)
In-Reply-To: <1010606104439.ZM1317@candle.brasslantern.com>; from schaefer@candle.brasslantern.com on Wed, Jun 06, 2001 at 10:44:39AM +0000


On Wed, Jun 06, 2001 at 10:44:39AM +0000, Bart Schaefer wrote:
> You have it backwards.  Clint wants check_dump_file() to search for a
> function in the already-mapped files because load_dump_header() fails
> if it can't do an open().

Right.

> The problem I see with it is that it could cause mysterious violations
> of fpath ordering.  I guess it wouldn't be so bad if it were only the
> fallback case exactly when load_dump_header() can't open().

On Wed, Jun 06, 2001 at 01:14:18PM +0200, Sven Wischnowsky wrote:
> Note that check_dump_file() does search mapped files, but only if
> try_dump_file() could stat the file to compare st_ino and st_dev.

> I think I actually considered saving only the filename in the funcdump
> struct and compare that (for the equality test, we'd still need
> something like that to find out which is the youngest file).

On Wed, Jun 06, 2001 at 03:21:04PM +0400, Andrej Borsenkow wrote:
> Will this help?
> 
> int fstat(int fildes, struct stat *buf);

I suppose that would also obviate the need for storing the
filename in funcdump.


      parent reply	other threads:[~2001-06-06 14:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-03 16:45 Clint Adams
2001-06-06  9:47 ` Sven Wischnowsky
2001-06-06 10:44   ` Bart Schaefer
2001-06-06 11:14     ` Sven Wischnowsky
2001-06-06 11:21       ` Andrej Borsenkow
2001-06-06 14:25   ` Clint Adams [this message]

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=20010606102557.B23921@dman.com \
    --to=clint@zsh.org \
    --cc=zsh-workers@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).