From: haahr@kaleida.com (Paul Haahr)
To: Arnold Robbins <arnold@cc.gatech.edu>
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: forking builtins
Date: Thu, 23 Sep 1993 18:02:26 -0400 [thread overview]
Message-ID: <9309232100.AA00244@talisman.kaleida.com> (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.
it's not that hard conceptually, it just takes some effort to make sure
you catch every reference to file descriptors. Byron and i came up with
a strategy for es that works. see es's fd.c for details.
but strenuous it is not.
>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.
echo could also use it.
next reply other threads:[~1993-09-23 21:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-09-23 22:02 Paul Haahr [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-09-24 21:19 Tom Culliton x2278
1993-09-24 16:40 Alan Watson
1993-09-24 0:03 Tom Culliton x2278
1993-09-23 18:57 Arnold Robbins
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=9309232100.AA00244@talisman.kaleida.com \
--to=haahr@kaleida.com \
--cc=arnold@cc.gatech.edu \
--cc=rc@hawkwind.utcs.toronto.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).