From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
<zsh-workers@sunsite.auc.dk>
Subject: RE: Precompiled wordcode zsh functions
Date: Tue, 29 Feb 2000 11:15:33 +0300 [thread overview]
Message-ID: <000701bf828d$261408b0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <200002290745.IAA08900@beta.informatik.hu-berlin.de>
>
> Yep. In my implementation digest files are really only one-file-
> directories. I.e. they are searched like normal directories by
> getfpfunc() (more precisely a utility function used by it). It will
> not define all functions in the digest file immediatly. I really
> prefer that behaviour because a user has to worry about nothing when,
> for example, he wants to override one of the functions with his own
> definition in a directory earlier in $fpath.
>
Yep, after thinking about it a bit more I believe this is the "least
confusing" case. Unfortunately, here is where kshautoload cuts in :-) Does
your digest handle it currently? What happens with
autoload foo
contents of foo:
some prolog code
bar1() { }
bar2() { }
foo() { }
I'd expect, that bar1, bar2 and foo were (re-)defined as just reference to
already compiled code (actually, true for every funtction possibly defined
in zwc file).
/andrej
next prev parent reply other threads:[~2000-02-29 8:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-29 7:45 Sven Wischnowsky
2000-02-29 8:15 ` Andrej Borsenkow [this message]
2000-02-29 8:21 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
2000-02-29 11:42 Sven Wischnowsky
2000-02-29 7:52 Sven Wischnowsky
2000-02-28 10:07 Sven Wischnowsky
2000-02-28 14:50 ` Sven Wischnowsky
2000-02-28 18:18 ` Zefram
2000-02-29 4:22 ` Bart Schaefer
2000-02-25 11:31 Sven Wischnowsky
2000-02-25 10:42 Sven Wischnowsky
2000-02-25 17:35 ` Bart Schaefer
2000-02-25 8:41 PATCH: parser (was: Re: PATCH: Improved _mailboxes) Sven Wischnowsky
2000-02-25 9:44 ` Precompiled wordcode zsh functions 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='000701bf828d$261408b0$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=wischnow@informatik.hu-berlin.de \
--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).