From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Naive question: how hard are namespaces for functions
Date: Wed, 17 May 2017 15:43:37 -0700 [thread overview]
Message-ID: <170517154337.ZM27772@torch.brasslantern.com> (raw)
In-Reply-To: <etPan.591c5c23.79e2a9e3.6b4c@MacMini.local>
On May 17, 4:20pm, Sebastian Gniazdowski wrote:
}
} Maybe namespaces are easy?
This depends entirely on what you mean by "namespaces".
Voluntarily naming functions with an identifiable prefix string is easy.
Calling those functions by a name other than the full name with the
prefix string is probably of middling difficulty, but would require
some sort of collision resolution if the same suffix appeared with two
or more prefixes.
Dividing $functions (or any hash parameter value) up into named sections
that the shell somehow understands natively, is very difficult.
I'm not following what this would have to do with how long it takes to
load function definitions.
next prev parent reply other threads:[~2017-05-17 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 8:24 Sebastian Gniazdowski
2017-05-17 14:20 ` Sebastian Gniazdowski
2017-05-17 22:43 ` Bart Schaefer [this message]
2017-05-18 10:29 ` Sebastian Gniazdowski
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=170517154337.ZM27772@torch.brasslantern.com \
--to=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).