From mboxrd@z Thu Jan  1 00:00:00 1970
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <df49a7370712110532v236cf4bbx87678b4d67dc674c@mail.gmail.com>
References: <33F4A474-6B5E-4A40-8361-A131770B900F@mac.com>
	<20071201190953.GA788@shodan.homeunix.net>
	<df49a7370712110532v236cf4bbx87678b4d67dc674c@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <74D6B736-B261-44EC-B2AF-86ACC35E971A@mac.com>
Content-Transfer-Encoding: 7bit
From: Pietro Gagliardi <pietro10@mac.com>
Subject: Re: [9fans] rc: token buffer too short
Date: Tue, 11 Dec 2007 14:46:34 -0500
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Topicbox-Message-UUID: 15423d3a-ead3-11e9-9d60-3106f5b1d025

Not in this case, no. The format of awk is

	awk 'program' files
	awk -f prgm files

What I could do instead is

	u=/tmp/$0$pid$apid$0
	cat > $u <<\END
	program
	END
	awk -f $u $*
	rm $u

but I'd rather not go that way to avoid possible collisions.

Here's another problem. The error check function cats to [1=2].  
However, instead of going to standard output, it makes a file [1=2]  
and writes the message there. How do I fix this?

On Dec 11, 2007, at 8:32 AM, roger peppe wrote:

> a reason to use here files? :-)
>
> On Dec 1, 2007 7:09 PM, Martin Neubauer <m.ne@gmx.net> wrote:
>> Apparrently in quoted strings each character (rune, actually)  
>> constitutes
>> one token. The lexical scanner only holds NTOK (==8192) tokens at  
>> a time and
>> sam and wc convince me you have a 8555 byte string you pass to  
>> awk. You
>> should probably put the awk stuff into a separate file eg.awk and  
>> just do
>> `awk -f eg.awk $*' in eg (cf. chem(1) ). You might have to fiddle  
>> with where
>> you put things, but that seems to be the easiest way out.
>>
>>         Martin
>>
>>
>> * Pietro Gagliardi (pietro10@mac.com) wrote:
>>> Run /n/sources/contrib/pietro/eg (a work-in-progress troff
>>> preprocessor for graphs of equations). You get the error described
>>> above on a line that contains simply "else". What happened?
>>