From: haahr@mv.us.adobe.com (Paul Haahr)
To: culliton@srg.af.mil
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: Speed of rc
Date: Thu, 8 Apr 1993 19:09:58 -0400 [thread overview]
Message-ID: <9304082309.AA16094@astro.mv.us.adobe.com> (raw)
ok, now i understand what's going on. yes, if you use test a lot in rc,
it will go slowly. if your /bin/sh has a test builtin, that will run faster.
there's no surprises here, you're just comparing apples and oranges.
i think that there are two very good reasons that test is not built into rc:
(1) with one glaring exception (echo), rc really has no extraneous builtins,
and (2) the semantics of test are, at best, awful. in addition, i know that
Byron hesitated before deviating seriously from the bell labs version of rc.
personally, if test had nice semantics, i would prefer to see it built in
to rc. it doesn't.
paul
ps: as many of you know, Byron and i have been doing a new shell, es, in
which we felt no obligation to be compatible with rc. es needed to have
a builtin for doing some test-like things because path-searching is done
by functions written in es rather than c. because of this, we exposed an
access function, which does many things that test does, albeit cleaner.
next reply other threads:[~1993-04-08 23:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-04-08 23:09 Paul Haahr [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-04-15 20:26 speed " Tom Culliton x2278
1993-04-13 20:26 Byron Rakitzis
1993-04-13 21:23 ` John Mackin
1993-04-13 23:42 ` mycroft
1993-04-12 5:51 Speed " Paul Haahr
1993-04-09 15:58 Tom Culliton x2278
1993-04-08 22:31 Tom Culliton x2278
1993-04-09 0:38 ` Scott Schwartz
1993-04-09 15:23 ` John Mackin
1993-04-13 19:26 ` Chris Siebenmann
1993-04-13 21:13 ` John Mackin
1993-04-09 16:32 ` Dave Mason
1993-04-09 16:39 ` John Mackin
1993-04-09 19:22 ` Dave Mason
1993-04-09 21:12 ` Chris Siebenmann
1993-04-08 20:14 Byron Rakitzis
1993-04-08 15:45 Paul Haahr
1993-04-07 19:50 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:
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=9304082309.AA16094@astro.mv.us.adobe.com \
--to=haahr@mv.us.adobe.com \
--cc=culliton@srg.af.mil \
--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).