Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Autoloading of compctl from dbm database file.
- X-seq: zsh-workers 2502
- From: Bart Schaefer <schaefer@xxxxxxx>
- To: Zefram <zefram@xxxxxxxxxxxxxxxxx>, fclim@xxxxxxxxxxxxxx (Fung-Chai Lim), zsh-workers@xxxxxxxxxxxxxxx
- Subject: Re: Autoloading of compctl from dbm database file.
- Date: Sat, 30 Nov 1996 15:16:26 -0800 (PST)
- In-reply-to: Zefram <zefram@xxxxxxxxxxxxxxxxx> "Re: Autoloading of compctl from dbm database file." (Nov 30, 4:40pm)
- References: <8922.199611301640@xxxxxxxxxxxxxxxxxxxxxxx>
- Reply-to: schaefer@xxxxxxxxxxxxxxxx
Seems to me that this idea has "module" written on it, in large flashing
purple neon letters.
On Nov 30, 4:40pm, Zefram wrote:
> Subject: Re: Autoloading of compctl from dbm database file.
>
> We already have a function autoloading facility. Aliases are cheap to
> store, usually short, and people don't have so many of them. I think
> it is therefore not worth adding the database autoloading for them.
> However, a dbm database may be a good solution to the problem of
> autoloading compctls.
Compctls aren't very expensive to store either, are they? The slow
part of loading compctls and functions is parsing. If we're going
to introduce a database, we might as well also introduce a binary
storage format and put pre-"compiled" functions, compctls, etc. in
there. Using a database just to store text that zsh then has to parse
and execute anyway doesn't seem very helpful.
Further -- I admit I haven't tried the patch -- doesn't attempting to
autoload compctls, even from a database, slow down default completion
a lot?
Messages sorted by:
Reverse Date,
Date,
Thread,
Author