From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from smtp2.libero.it ([193.70.192.52]) by hawkwind.utcs.toronto.edu with SMTP id <25708>; Tue, 9 May 2000 18:54:15 -0400
Received: from LocalHost (151.32.162.205) by smtp2.libero.it; 9 May 2000 10:29:54 +0200
Received: from carlos by localhost with local (Exim 2.05 #1 (Debian))
	id 12p5Hj-0002AD-00; Tue, 9 May 2000 10:22:31 +0200
Date:	Tue, 9 May 2000 04:22:31 -0400
From:	Carlo Strozzi <carlos@linux.it>
To:	rc@hawkwind.utcs.toronto.edu
Subject: Re: building rc on QNX4
Message-ID: <20000509102231.A8231@tango.iol.it>
Reply-To: carlos@texne.com
Mail-Followup-To: rc@hawkwind.utcs.toronto.edu
References: <20000508151502.23583.qmail@pantransit.reptiles.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <20000508151502.23583.qmail@pantransit.reptiles.org>; from smarry@vex.net on Mon, May 08, 2000 at 11:15:02AM -0400
Organization: TeXne.COM

On Mon, May 08, 2000 at 11:15:02AM -0400, Smarasderagd wrote:
 (...)
 >replacing ` with ``($nl) if I really want lines and not tokens. If the
 >input is big enough to cause problems for rc, I switch to awk, sed, or
 >whatever.  Complicated interactive scripts I usually write in awk/gawk.

awk and sed are great tools, but the problem with awk is that any
interactions with external utilities spawns an extra /bin/sh process,
wich sucks a hell of a lot in Web CGI scripts. That's why using a shell
in the first place, with a bit of care, tends to be more efficient.
And awk does not even have an 'exec' facility, that would also help with
saving processes.

bye  -carlo
-- 
I can read MIME or uuencoded e-mail attachments in PDF, Postscript, HTML,
RTF or text formats. Please do not send Word or Excel files.