From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Zefram <zefram@tao.co.uk>
Cc: zsh-workers@math.gatech.edu
Subject: Re: Variable namespaces, goals for ZLE, etc.
Date: Wed, 10 Jun 1998 10:37:28 -0700 [thread overview]
Message-ID: <980610103728.ZM12142@candle.brasslantern.com> (raw)
In-Reply-To: <199806101055.LAA13182@taos.demon.co.uk>
On Jun 10, 11:55am, Zefram wrote:
} Subject: Re: Variable namespaces, goals for ZLE, etc.
}
} The advantage of a "zsh." prefix is that *nothing* currently relies
} on such a variable name existing or behaving in any particular manner,
} whereas "ZSH_" names are defined by POSIX to have no special semantics.
Are there any "available" names in the POSIX space?
The problem with introducing an incompatible syntax in order to escape
POSIX is that you can't reliably export variables with the new names.
I've used versions of sh that would mangle the environment and/or issue
warning messages if there were any strings present where the stuff to
the left of the `=' contained characters other than [A-Z][a-z][0-9]_.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1998-06-10 17:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-09 17:09 User-defined zle widgets and built-in widget failure Bart Schaefer
1998-06-09 18:01 ` Zefram
1998-06-09 19:12 ` Bart Schaefer
1998-06-09 20:02 ` Zefram
1998-06-10 6:26 ` Variable namespaces, goals for ZLE, etc Bart Schaefer
1998-06-10 10:55 ` Zefram
1998-06-10 17:37 ` Bart Schaefer [this message]
1998-06-10 18:01 ` Zefram
1998-06-10 18:36 ` Bart Schaefer
1998-06-10 10:24 ` Associative arrays, structured namespaces Bruce Stephens
1998-06-10 10:44 ` Zefram
1998-06-10 12:07 ` Bruce Stephens
1998-06-10 12:28 ` Bruce Stephens
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=980610103728.ZM12142@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zefram@tao.co.uk \
--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).