From: Christoph Kappel <unexist@dorfelite.net>
To: <schaefer@brasslantern.com>
Cc: <zsh-workers@zsh.org>
Subject: Re: Added builtins per runtime
Date: Sat, 01 May 2010 23:02:28 +0200 [thread overview]
Message-ID: <12855ad6dba.6318419370147111815.5595086135333789265@dorfelite.net> (raw)
In-Reply-To: <z2o691a5d911005011349j14613f73g432036f224d86377@mail.gmail.com>
That was exactly my question. Can a module change it's features per runtime?
Generally the use of the word feature in the doc is really confusing, reading the
coding makes it's even worse when a feature struct contains lists of builtins,
condistions etc. which are called features too.
The doc also doesn't make very clear what abstracts.
I basically want to provide a builtin/feature/whatever that provides a way to add
actions in another language - ruby in my case.
---- On Sat, 01 May 2010 22:49:48 +0200 Bart Schaefer <schaefer@brasslantern.com> wrote ----
>On Sat, May 1, 2010 at 1:17 PM, Christoph Kappel <unexist@dorfelite.net> wrote:
>>
>> I want to add new ones per runtime.I am currently trying to maintain a second list
>> and call addbuiltin() when I need to add one.
>
>I guess I'm not understanding the question, then. Can you give an
>example of what it means to you to "add new ones per runtime"? What
>would it mean for example.c to "change" the builtins that it defines?
>
>Modules define features, which can be several different kinds of
>things including builtins. None of a module's features is available
>until the module is loaded. Once a module is loaded, you can't alter
>the set of features it provides, though the zmodload command can
>enable and disable specific features to make them visible or invisible
>to the shell.
>
>So typically a module would define several features and the calling
>shell script/program would determine which ones it wishes to enable or
>disable. How does that differ from what you are attempting to
>accomplish?
>
next prev parent reply other threads:[~2010-05-01 21:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-01 16:33 Christoph Kappel
2010-05-01 19:58 ` Bart Schaefer
2010-05-01 20:17 ` Christoph Kappel
2010-05-01 20:49 ` Bart Schaefer
2010-05-01 21:02 ` Christoph Kappel [this message]
2010-05-02 9:08 ` Bart Schaefer
2010-05-02 17:28 ` Christoph Kappel
2010-05-03 18:57 ` Peter Stephenson
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=12855ad6dba.6318419370147111815.5595086135333789265@dorfelite.net \
--to=unexist@dorfelite.net \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/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).