From: "rob pike, esq." <r@geekmail.cc>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] v8 shell
Date: Thu, 13 Nov 2003 09:41:24 -0800 [thread overview]
Message-ID: <e004e732ced8e1653a716c793de55e43@google.com> (raw)
In-Reply-To: <20031113160648.GB21872@localhost.localdomain>
i fought fairly hard to get the key features of the v8 shell adopted
into posix. these included exportable functions and output from
commands like whatis that could be read as input. but i didn't fight
hard enough because i didn't fight at every single committee meeting.
as soon as i stopped going, the changes were reverted ("thank god he's
gone"). the experience soured me for life on contributing to
standards committees.
for example, the 'builtin' trick in modern shells comes out of the v8
shell but the other half is missing.
korn shell or bash:
$ type cd
cd is a shell builtin
$
v8 shell:
$ whatis cd
builtin cd
$
see the difference? the latter is executable code. why was it important
to `fix' this in the committee? bitterness rules.
maybe that's why rc happened. probably was a factor. i know i asked
td to design rc, but i also did the work in creating the v8 shell. i
don't really remember.
-rob
next prev parent reply other threads:[~2003-11-13 17:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.21.0311131606190.27715-100000@zenon.ceid.upatras.gr>
2003-11-13 16:06 ` Taj Khattra
2003-11-13 17:41 ` rob pike, esq. [this message]
2003-11-13 23:44 ` George Michaelson
2003-11-14 0:43 ` rog
2003-11-14 6:59 ` boyd, rounin
2003-11-17 10:26 ` Douglas A. Gwyn
2003-11-17 12:13 ` Charles Forsyth
2003-11-18 9:48 ` Douglas A. Gwyn
2003-11-14 12:04 ` John Murdie
2003-11-14 18:01 ` rog
2003-11-14 19:04 ` boyd, rounin
2003-11-14 19:18 ` rog
2003-11-14 19:31 ` boyd, rounin
2003-11-14 22:25 ` Roman Shaposhnick
2003-11-16 11:45 ` Richard Miller
2003-11-16 12:01 ` Geoff Collyer
2003-11-16 12:21 ` Richard Miller
2003-11-17 20:31 ` rog
2003-11-16 14:23 ` Russ Cox
2003-11-16 14:35 ` Richard Miller
2003-11-15 15:03 ` a
[not found] ` <oprykztjlztsux9g@smtp.borf.com>
2003-11-14 0:41 ` boyd, rounin
2003-11-14 17:51 ` rog
2003-11-14 18:51 ` boyd, rounin
2003-11-17 10:26 ` Douglas A. Gwyn
2003-11-14 7:05 ` boyd, rounin
2003-11-14 8:13 boyd, rounin
2003-11-14 18:12 Richard C Bilson
2003-11-14 19:09 ` rog
2003-11-14 19:12 ` boyd, rounin
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=e004e732ced8e1653a716c793de55e43@google.com \
--to=r@geekmail.cc \
--cc=9fans@cse.psu.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.
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).