From: Zefram <A.Main@dcs.warwick.ac.uk>
To: hzoli@cs.elte.hu (Zoltan Hidvegi)
Cc: schaefer@nbn.com, gjb@moa.cs.duke.edu, zsh-workers@math.gatech.edu
Subject: Re: Distribution terms
Date: Tue, 27 Aug 1996 21:20:42 +0100 (BST) [thread overview]
Message-ID: <6222.199608272020@stone.dcs.warwick.ac.uk> (raw)
In-Reply-To: <199608271925.VAA08321@bolyai.cs.elte.hu> from "Zoltan Hidvegi" at Aug 27, 96 09:25:28 pm
> And in zsh-3.1 we have to find
>out a portable way to use dynamically loadable modules. After that anyone
>can write a plug-in for zsh and can implement any feature he wants. But
>such features should not blow up zsh.
I doubt that you'll find a way to do dynamic loading on every Unix. It
might be best to simply restrict such features to Unices where the ELF
library is available (dlopen(), etc.) -- this would avoid a lot of
complication.
> It would be a good idea to better
>modularise the existing zsh code, make a few things optional (fo rexample
>zle and completion).
I think it would be a good idea to have a configure-time option to
exclude ZLE, even where it can't be dynamically loaded. Simple
conditional compilation could do this. We might also want to consider
a configuration option to build a restricted shell -- this is a major
feature that most other shells already have.
Another thing we might want to do is to optionally have basic
file-manipulation commands (mv, rm, etc.) as builtins. Maybe some
administration commands (mount, mknod) too. The purpose of this would
be that we could have a statically-linked zsh in /sbin for when the
system is hosed. (I'd support making sync a builtin even in the
standard version.)
> I do not know how much is the ovehead caused by a big
>executable. When zsh is used as a scipt interpreter on a demand-paged
>system only the parts necessary run a script will be loaded so it may not
>give any real improvement.
There's not much speed improvement, and actually loading a module
separate from the executable will cause a penalty. This penalty won't
be a problem unless it is incurred on every invocation -- we should
definitely avoid doing this.
-zefram
next prev parent reply other threads:[~1996-08-27 20:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-08-15 18:17 zsh-3.0.0 released Zoltan Hidvegi
1996-08-15 18:57 ` zsh-3.0.0 installed in the US Tom Kaczmarski
1996-08-16 4:18 ` Andrew Cosgriff
1996-08-16 11:55 ` Tom Kaczmarski
1996-08-20 1:32 ` Andrew Cosgriff
1996-08-20 12:55 ` Tom Kaczmarski
1996-08-15 19:56 ` zsh-3.0.0 released John Harres
1996-08-15 20:14 ` Richard Coleman
1996-08-15 20:27 ` John Harres
1996-08-15 21:22 ` Richard Coleman
1996-08-15 21:35 ` Wayne Davison
1996-08-27 14:25 ` Distribution terms Greg J. Badros
1996-08-27 15:28 ` Bart Schaefer
1996-08-27 15:37 ` Bruce Stephens
1996-08-27 17:04 ` Greg J. Badros
1996-08-27 18:58 ` Bart Schaefer
1996-08-27 19:04 ` Zefram
1996-08-27 19:25 ` Zoltan Hidvegi
1996-08-27 19:53 ` future of zsh Richard Coleman
1996-08-27 16:32 ` zsh: future and loadable modules Chip Salzenberg
1996-08-28 9:03 ` Bruce Stephens
1996-08-27 20:23 ` future of zsh Zoltan Hidvegi
1996-08-27 20:20 ` Zefram [this message]
1996-08-27 20:32 ` Distribution terms Zoltan Hidvegi
1996-08-27 16:37 ` Richard Coleman
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=6222.199608272020@stone.dcs.warwick.ac.uk \
--to=a.main@dcs.warwick.ac.uk \
--cc=gjb@moa.cs.duke.edu \
--cc=hzoli@cs.elte.hu \
--cc=schaefer@nbn.com \
--cc=zsh-workers@math.gatech.edu \
/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).