zsh-workers
 help / color / mirror / code / Atom feed
From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: coleman@math.gatech.edu (Richard Coleman)
Cc: zsh-workers@math.gatech.edu
Subject: Re: future of zsh
Date: Tue, 27 Aug 1996 22:23:47 +0200 (MET DST)	[thread overview]
Message-ID: <199608272023.WAA08708@bolyai.cs.elte.hu> (raw)
In-Reply-To: <199608271953.PAA25249@redwood.skiles.gatech.edu> from Richard Coleman at "Aug 27, 96 03:53:06 pm"

Richard wrote:
> As to zle and completion, it would be great if this could be moved
> to a module, or to a seperate library.  I had similar ideas when I was
> maintainer.  Unfortunately, zle and completion use so many of the
> internal data structures (just about all of them actually), this would be
> very difficult.  I believe a better idea is to move some of the

That's not a problem.  A mudule can use any zsh internal function/variable
etc.  The important thing is that the main code should not use anything
from the module.  The main part of zsh does not use zle + completion as I
know except the read builtin and the compctl builtin.  The later should
probably be moved into a separate file.

Adding loadable modules on an elf system is trivial (I have already done
that on linux) and it is probably not difficult on other systems which
support dlopen/dlclose/dlsym.  On systems modules cannot be statically
linked to zsh as a compile-time option.  The difficult part is to write
configure tests about how to compile and link dynamic modules and figure
out a consistent interface.

> internals of the completion code into the hash table code.  This was
> part of the motivation when I rewrote the hash table code.  Essentially
> each object would know how to complete itself.  Again, this is non-trivial,
> but a worthwhile goal.  I believe that a general mechanism for hash table
> searching would simplify both the completion code and the spell checking
> code.

Yes, it may be doable.  The zsh code gradually becomes more and more
object-orientated.

> zsh 3.0 is a great increase in modularity over previous version, as well
> as being much more maintainable (take a look at the zsh 2.5.03 code if
> you don't believe me).  But I believe this is a process that should

Oh, I believe it.  I've seen parts of it.

> continue.  In particular, the exec.c code is still somewhat of a mess.  If
> I find some time, I will probably do some work on this myself.

That would be great.  When you do that do not forget to use a profiler.
Sometimes I think I understand most of exec.c but then I wake up.

Zoltan


  parent reply	other threads:[~1996-08-27 20:23 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         ` Zoltan Hidvegi [this message]
1996-08-27 20:20       ` Distribution terms Zefram
1996-08-27 20:32         ` 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=199608272023.WAA08708@bolyai.cs.elte.hu \
    --to=hzoli@cs.elte.hu \
    --cc=coleman@math.gatech.edu \
    --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).