From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: zrecompile
Date: Mon, 3 Apr 2000 10:01:15 +0000 [thread overview]
Message-ID: <1000403100115.ZM18748@candle.brasslantern.com> (raw)
In-Reply-To: <200004030839.KAA13283@beta.informatik.hu-berlin.de>
In-Reply-To: <200004030945.LAA31042@beta.informatik.hu-berlin.de>
On Apr 3, 10:39am, Sven Wischnowsky wrote:
} Subject: Re: zrecompile
}
} And another thing: the zwc files till use $ZSH_VERSION in the header
} to test for compatibility -- somehow I didn't like to add an additional
} version number scheme for them, but it would be better, I think (the
} format will certainly change less often than $ZSH_VERSION).
Yea, but it'll be much less recognizable in the -t output. I think the
$ZSH_VERSION test is fine.
On the other hand, that should be put in some immutable part of the file
header so that *any* version of zsh can be guaranteed to be able to read
it back -- to rephrase, we set the requirement NOW that changes to the
format of the header must only come *after* the version string (or some
equivalent requirement), so that it's always possible to display the
version mismatch (or at least know that was the reason for the error).
On Apr 3, 11:45am, Sven Wischnowsky wrote:
}
} zrecompile probably makes a whole lot more sense when used with the -p
} option, because then it also catches new functions in directories.
}
} Maybe we should make that the default and the automatic zwc file
} searching only be done when given some option.
My instinct is to say that it's OK the way it is; but I haven't used it
very much, so ...
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-04-03 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-03 8:39 zrecompile Sven Wischnowsky
2000-04-03 9:45 ` zrecompile Sven Wischnowsky
2000-04-03 10:01 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-04-02 10:01 zrecompile Andrej Borsenkow
2000-04-03 1:29 ` zrecompile 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=1000403100115.ZM18748@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.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).