Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: notesfiles
Path: utzoo!linus!decvax!ittvax!dcdwest!sdcsvax!sdcrdcf!hplabs!hp-pcd!hpfcla!ajs
From: ajs@hpfcla.UUCP
Newsgroups: net.unix
Subject: Re: Re: Interesting Bourne shell usage,
Message-ID: <43800010@hpfcla.UUCP>
Date: Tue, 22-May-84 23:07:00 EDT
Article-I.D.: hpfcla.43800010
Posted: Tue May 22 23:07:00 1984
Date-Received: Fri, 1-Jun-84 07:42:20 EDT
References: <142@ho95b.UUCP>
Organization: Hewlett-Packard Fort Collins Systems Division - Fort Collins, CO
Lines: 12
Nf-ID: #R:ho95b:-14200:hpfcla:43800010:000:534
Nf-From: hpfcla!ajs    May 27 22:07:00 1984

> Another note on this is that /bin/sh forks off a process to do
> the for loop when directing its output to a pipe; ksh doesn't.
> This feature, and builtins for echo and expr considerably speed
> up shell script execution in ksh.

Yes, and Bourne shell users beware:  That  "invisible  fork" can lead to
some  real   confusion,  if  you  modify  a  shell  variable   within  a
meta-construct  which  is  redirected.  Don't  expect  the  value  to be
correct after the end of the construct!

Looking forward to ksh,
Alan Silverstein