From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <86ipusd1wr.fsf@cmarib.ramside>
References: <86fwpz55nj.fsf@cmarib.ramside>
	<257867.782e4d7b.wsc0.mx@tumtum.plumbweb.net>
	<5ddd9deccbea5e8556dfc0c228b63311@ladd.quanstro.net>
	<BANLkTik=fh5sAr5cR+PRNGD+LJETeOgyqA@mail.gmail.com>
	<86vcythf8h.fsf@cmarib.ramside>
	<BANLkTi=Lhkqh2dAhg+j5s6i33zCx3GJmfA@mail.gmail.com>
	<BANLkTikp1+FD6kC5HTq0tvfXeFQ03ySGfw@mail.gmail.com>
	<86ipusd1wr.fsf@cmarib.ramside>
Date: Tue,  5 Apr 2011 22:50:12 +0300
Message-ID: <BANLkTi=yFornXsZWuBhmAqufXj5seMhGNw@mail.gmail.com>
From: Yaroslav <yarikos@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] Making read(1) an rc(1) builtin?
Topicbox-Message-UUID: caf1fc26-ead6-11e9-9d60-3106f5b1d025

2011/4/5  <smiley@zenzebra.mv.com>:
> I think string parsing and numeric comparisons are reasonable features
> to include in almost any programming language. =C2=A0I think having
> primitives for line-oriented input and line-oriented output are more
> than appropriate for a line-oriented language like rc(1). =C2=A0As it sta=
nds,
> rc(1) can have it's cake, but it can't eat it without a fork(2).

As it was stated earlier, a fork(2) is rather cheap here, so what's
your concern then?
Maybe it's time to forget the lectures about expensive forks and just cary =
on?
I bet you won't even notice much changes in your stats -c graph.