From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from netcomsv.netcom.com ([163.179.1.14]) by hawkwind.utcs.toronto.edu with SMTP id <2192>; Tue, 21 Sep 1993 12:44:39 -0400
Received: from netapp.UUCP by netcomsv.netcom.com with UUCP (4.1/SMI-4.1)
	id AA26668; Tue, 21 Sep 93 09:44:56 PDT
Received: by netapp.com (4.1/SMI-4.1)
	id AA09070; Tue, 21 Sep 93 09:36:23 PDT
Date:	Tue, 21 Sep 1993 12:36:23 -0400
From:	byron@netapp.com (Byron Rakitzis)
Message-Id: <9309211636.AA09070@netapp.com>
To:	cks@hawkwind.utcs.toronto.edu, rc@hawkwind.utcs.toronto.edu
Subject: Re: Thoughts on a builtin read

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?