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: Fri, 13 Aug 2004 23:30:49 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Hans Horn cc: cygwin AT cygwin DOT com Subject: Re: igawk problem In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.39 On Fri, 13 Aug 2004, Hans Horn wrote: > Group, > > I have a rather lengthy awk script (that internally includes a bunch of awk > library functions; therefore I'm using igawk). > > When I invoke it, e.g. like > > echo | igawk -f script.awk > eval: gawk: argument list too long > > The script and the awk library functions together make up approx. 34kByte. > > Does anybody have a clue whether I'm running here into a hard shell limit, > or some internal limit of gawk? This looks like an upstream igawk portability bug -- the lines processed_program=`gawk -- "$expand_prog" /dev/stdin <