Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Mon, 16 Aug 2004 20:17:26 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Yitzchak Scott-Thoennes cc: cygwin AT cygwin DOT com Subject: Re: igawk problem In-Reply-To: <20040815183517.GA3512@efn.org> Message-ID: References: <20040815183517 DOT GA3512 AT efn DOT org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.39 On Sun, 15 Aug 2004, Yitzchak Scott-Thoennes wrote: > 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 < > $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. Ah, but I wasn't suggesting that. I was thinking of using xargs to invoke gawk with one long argument, instead of passing it on the command line... However, now that I think of it, that's probably no different than running it from the shell... Oh, well... I guess Hans's solution with mktemp is the best under the circumstances. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "Happiness lies in being privileged to work hard for long hours in doing whatever you think is worth doing." -- Dr. Jubal Harshaw -- 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/