From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@labs.coraid.com>
Date: Thu, 13 May 2010 10:23:45 -0400
To: 9fans@9fans.net
Message-ID: <84f53dabe8357c852216d6c9024f6eb0@coraid.com>
In-Reply-To: <op.vcndg3knhipq0d@santucco.avp.ru>
References: <AANLkTinmbNhBI_V3bvIctfCXdNwzhYNjtoDaA7Mcc3D7@mail.gmail.com>
	<op.vck9apb3hipq0d@santucco.avp.ru>
	<AANLkTin7F2mT7yhs4VQATcvoIsKMDjsYwDzQX2sN6zyV@mail.gmail.com>
	<op.vcmv3401hipq0d@santucco.avp.ru>
	<158d5dc0571fa04cab44a99b3fdf5921@kw.quanstro.net>
	<op.vcndg3knhipq0d@santucco.avp.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] hoc output format
Topicbox-Message-UUID: 203875a8-ead6-11e9-9d60-3106f5b1d025

> > echo 1 2 | hoc -e '{while(read(x) != 0)y += x' ^ $nl ^ ' print y, "\n"}'
>
> Maybe it makes a sense to add in hoc(1) expression delimiter like a ';'?

i don't use hoc very often.  i tend to use acid.  (!)
this is because hoc won't do bit operations and doesn't
accept hex.

i typically do programming calculations and floating point
just isn't the right way to do that.

- erik