From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: text/plain; charset="utf-8"; format=flowed; delsp=yes
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
References: <AANLkTinmbNhBI_V3bvIctfCXdNwzhYNjtoDaA7Mcc3D7@mail.gmail.com>
	<op.vck9apb3hipq0d@santucco.avp.ru>
	<AANLkTin7F2mT7yhs4VQATcvoIsKMDjsYwDzQX2sN6zyV@mail.gmail.com>
	<op.vcmv3401hipq0d@santucco.avp.ru>
	<158d5dc0571fa04cab44a99b3fdf5921@kw.quanstro.net>
Date: Thu, 13 May 2010 18:06:29 +0400
MIME-Version: 1.0
From: Alexander Sychev <santucco@gmail.com>
Message-ID: <op.vcndg3knhipq0d@santucco.avp.ru>
In-Reply-To: <158d5dc0571fa04cab44a99b3fdf5921@kw.quanstro.net>
User-Agent: Opera Mail/10.10 (Linux)
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] hoc output format
Topicbox-Message-UUID: 20316452-ead6-11e9-9d60-3106f5b1d025

On Thu, 13 May 2010 17:24:47 +0400, erik quanstrom <quanstro@quanstro.net=
> =20
wrote:

> On Thu May 13 03:51:56 EDT 2010, santucco@gmail.com wrote:
>> Yes, I'm agree, but with one exception - awk(1) separates a data from =
a
>> code, hoc(1) doesn't do it. So hoc(1) can be used for plain calculatio=
n
>> tasks, not for  processing input files with a data.
>
> both awk and hoc accept standard input

Yes, but for hoc(1) it can be some program, for awk(1) it can be a data =20
only :-) - that is what I meant :-)

> echo 1 2 | hoc -e '{while(read(x) !=3D 0)y +=3D x' ^ $nl ^ ' print y, "=
\n"}'

Maybe it makes a sense to add in hoc(1) expression delimiter like a ';'?

--=20
Best regards,
   santucco