From: Christian Neukirchen <chneukirchen@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] shell functions
Date: Sat, 27 Sep 2014 16:40:40 +0200 [thread overview]
Message-ID: <8738bdw2hj.fsf@gmail.com> (raw)
In-Reply-To: <CADSkJJWP=cdMxXFH_Oo04Cp2tTxfD6kTTeXx22N6BOBBmj3fLA@mail.gmail.com> (Russ Cox's message of "Fri, 26 Sep 2014 11:54:46 -0400")
Russ Cox <rsc@swtch.com> writes:
> Thanks to name space hygiene on td's part, the rc function space and the
> CGI variable space do not overlap, so rc already has no possible
> interaction with CGI, which is as it should be. I don't think it is super
> important to try to make rc defend against malicious environments, any more
> than it is to make it somehow defend against malicious $paths. If those are
> security-relevant, you've already lost.
The problem could be completely avoided if the '{}' were implicit, that
is, store
fn foo { echo bar }
as
fn#foo=echo bar
(Also, I heard Research Unix v8 sh(1) stored functions in the environment
as "foo(){ ... }", i.e. without =. So this never clashes with any
variable. Not sure if that works portably enough for plan9port, though.)
--
Christian Neukirchen <chneukirchen@gmail.com> http://chneukirchen.org
next prev parent reply other threads:[~2014-09-27 14:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAL0h+tWUCrwWoTSeLz+Kx1yqKwKqwDBZZbH7fLe-PWXjLSgWWw@mail.gmail.com>
2014-09-26 15:54 ` Russ Cox
2014-09-26 16:32 ` [9fans] " Kurt H Maier
2014-09-26 16:44 ` Skip Tavakkolian
2014-09-26 16:55 ` Kurt H Maier
2014-09-29 15:30 ` Russ Cox
2014-09-26 16:48 ` Bakul Shah
2014-09-27 14:40 ` Christian Neukirchen [this message]
2014-09-28 7:00 ` arisawa
2014-09-28 9:39 ` Richard Miller
2014-09-29 13:03 ` arisawa
2014-09-29 13:20 ` Charles Forsyth
2014-10-01 9:37 ` arisawa
2014-09-29 18:05 ` erik quanstrom
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=8738bdw2hj.fsf@gmail.com \
--to=chneukirchen@gmail.com \
--cc=9fans@9fans.net \
/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.
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).