From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
<zsh-workers@sunsite.auc.dk>
Subject: RE: PATCH: parser (was: Re: PATCH: Improved _mailboxes)
Date: Thu, 24 Feb 2000 10:47:46 +0300 [thread overview]
Message-ID: <000901bf7e9b$70e3ef40$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <200002231321.OAA00470@beta.informatik.hu-berlin.de>
>
> Here is the first of the two. As I said, this mainly makes the parser
> create wordcode directly, no more extra compilation phase.
>
>
Sounds really interesting ... Two questions.
Is the code position-independent?
Is now code-compiler separated from code-interpreter?
The main reason for these questions - is it possible to precompile Zsh
function, store it and then execute directly? This may be intersted in many
cases - primary use is completion. Precompile completion functions; put
byte-code in single file; mmap this file. I do not know about speed increase
(if any) - but it should dramatically reduce RAM footprint on multiuser
systems. Currently every shell compiles every function on it's own and it
goes in private memory - and that is real RAM (O.K., it is real swap on some
systems :-) mmap'ing precompiled byte-code would mean, that just a single
copy exists.
It may be useful to generalize it to allow byte-code be the contents of
variable. Then Zsh could simply execute the content of
mapfile[/path/to/precompiled/file] ... may be, not as directly - with
something like imaginal zcompiler module
zcodeload file
/andrej
next prev parent reply other threads:[~2000-02-24 7:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-23 13:21 Sven Wischnowsky
2000-02-23 16:45 ` Bart Schaefer
2000-02-23 18:58 ` Peter Stephenson
2000-02-24 7:47 ` Andrej Borsenkow [this message]
2000-02-24 8:54 Sven Wischnowsky
2000-02-24 9:07 Sven Wischnowsky
2000-02-24 18:08 ` Bart Schaefer
2000-02-24 10:03 Sven Wischnowsky
2000-02-25 8:41 Sven Wischnowsky
2000-02-25 9:55 ` Andrej Borsenkow
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='000901bf7e9b$70e3ef40$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).