Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Sun, 15 Aug 2004 11:35:17 -0700
From: Yitzchak Scott-Thoennes <sthoenna AT efn DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: igawk problem
Message-ID: <20040815183517.GA3512@efn.org>
References: <cfj317$os8$1 AT sea DOT gmane DOT org> <Pine DOT GSO DOT 4 DOT 58 DOT 0408132323001 DOT 594 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.58.0408132323001.594@slinky.cs.nyu.edu>
User-Agent: Mutt/1.4.1i
Organization: bs"d
X-IsSubscribed: yes

On Fri, Aug 13, 2004 at 11:30:49PM -0400, Igor Pechtchanski wrote:
> This looks like an upstream igawk portability bug -- the lines
> 
> 	processed_program=`gawk -- "$expand_prog" /dev/stdin <<EOF
> 	$program
> 	EOF
> 
> look like the culprit.  They should be using xargs instead...

Not true.  Running an awk program several times on a subsets of the
files, as xargs may do, isn't necessarily going to have the same
effect as running it once on all the files.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/