rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Arnold Robbins <arnold@cc.gatech.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: forking builtins
Date: Thu, 23 Sep 1993 14:57:43 -0400	[thread overview]
Message-ID: <199309231857.AA02580@penfold.cc.gatech.edu> (raw)

althouh i'm sure to be flamed for mentioning the name 'ksh', much of that
shell's performance comes from strenous effort to avoid forking of builtins
upon redirection.

i am not advocating that byron rework rc or anything like that. except for
read, it's not a major problem with the other builtiins, i'm just remarking
upon it.

             reply	other threads:[~1993-09-23 19:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-09-23 18:57 Arnold Robbins [this message]
1993-09-23 22:02 Paul Haahr
1993-09-24  0:03 Tom Culliton x2278
1993-09-24 16:40 Alan Watson
1993-09-24 21:19 Tom Culliton x2278

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199309231857.AA02580@penfold.cc.gatech.edu \
    --to=arnold@cc.gatech.edu \
    --cc=rc@hawkwind.utcs.toronto.edu \


* 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).