From: Clint Adams <clint@zsh.org>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: PATCH: check deleted .zwc files
Date: Fri, 8 Jun 2001 15:53:09 -0400 [thread overview]
Message-ID: <20010608155309.A6700@dman.com> (raw)
In-Reply-To: <010608124608.ZM5942@candle.brasslantern.com>; from schaefer@candle.brasslantern.com on Fri, Jun 08, 2001 at 12:46:08PM -0700
> I have a .zwc file for several functions. I update one of those functions.
> I then remove and rebuild the .zwc file. Now, stat() of the .zwc shows
> that it is newer than the function file, but any running zsh still has a
> mapped descriptor on the removed file. With this code:
> > if (stat(filename, buf)) {
[...]
> zwcstat() will cause zsh to decide that it can keep using the mapped copy,
> even though the function file is actually newer than the mapped copy.
Maybe I'm confused. If you've generated a new .zwc file, that stat()
will return 0, and the mapped copy won't even be considered.
> The only safe thing to do is to try the fstat() first, then stat(). To be
> really complete, if fstat() and stat() disagree zsh should throw out the
> mapped file and reload it, but that could get pretty tricky.
Too tricky for me.
next prev parent reply other threads:[~2001-06-08 19:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-08 18:17 Clint Adams
2001-06-08 18:50 ` Bart Schaefer
2001-06-08 19:04 ` Clint Adams
2001-06-08 19:46 ` Bart Schaefer
2001-06-08 19:53 ` Clint Adams [this message]
2001-06-09 5:37 ` Andrej Borsenkow
2001-06-10 11:11 ` Clint Adams
2001-06-09 20:58 ` Bart Schaefer
2001-06-10 11:34 ` Clint Adams
2001-06-13 5:03 ` Bart Schaefer
2001-06-13 8:59 ` Sven Wischnowsky
2001-06-13 10:22 ` Bart Schaefer
2001-06-18 7:31 ` Sven Wischnowsky
2001-06-09 10:05 ` Cygwin failure " Andrej Borsenkow
2001-06-09 17:42 ` Bart Schaefer
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=20010608155309.A6700@dman.com \
--to=clint@zsh.org \
--cc=schaefer@candle.brasslantern.com \
--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).