rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: byron@netapp.com (Byron Rakitzis)
To: cks@hawkwind.utcs.toronto.edu, rc@hawkwind.utcs.toronto.edu
Subject: Re: Thoughts on a builtin read
Date: Tue, 21 Sep 1993 12:36:23 -0400	[thread overview]
Message-ID: <9309211636.AA09070@netapp.com> (raw)

cks:
> If rc's read becomes a builtin version of line, I think we need some
>optimization of forks in rc, since currently
>	x = `BUILTIN
>results in rc forking.

I don't see how this could be avoided unless you define a whole
new i/o model internal to rc just for builtins and the backquote
splitter to use.

It looks like that would involve reinventing the OS inside rc, so it
would lead me to suggest that Unix fork is just broken (i.e., it should
be faster) but this is not a very productive avenue to pursue.

It's a shame when you can't use the Unix style when programming in
Unix. Is it time to move onto something else?


             reply	other threads:[~1993-09-21 16:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-09-21 16:36 Byron Rakitzis [this message]
1993-09-21 16:50 ` Chris Siebenmann
  -- strict thread matches above, loose matches on Subject: below --
1993-09-22 17:18 Steve_Kilbane
1993-09-21 17:26 Arnold Robbins
1993-09-21 17:11 rsalz
1993-09-21 16:58 Arnold Robbins
1993-09-21 16:52 gjv%atlas%cesar
1993-09-21 15:56 malte
1993-09-21 17:02 ` Chris Siebenmann
1993-09-21 15:54 Tom Culliton x2278
1993-09-21 15:15 Alan Watson
1993-09-21 15:09 rsalz
1993-09-21 14:33 malte
1993-09-21 14:20 rsalz
1993-09-21  6:51 malte
1993-09-21 14:19 ` Chris Siebenmann
1993-09-20 22:11 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=9309211636.AA09070@netapp.com \
    --to=byron@netapp.com \
    --cc=cks@hawkwind.utcs.toronto.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).