From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <84f53dabe8357c852216d6c9024f6eb0@coraid.com>
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>
	<84f53dabe8357c852216d6c9024f6eb0@coraid.com>
Date: Thu, 13 May 2010 17:09:33 +0200
Message-ID: <AANLkTimOiU62A_f6RatbWsE1VR9Xtwrbe-FLk2aO7uQa@mail.gmail.com>
From: Gorka Guardiola <paurea@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] hoc output format
Topicbox-Message-UUID: 2043ea1e-ead6-11e9-9d60-3106f5b1d025

On Thu, May 13, 2010 at 4:23 PM, erik quanstrom
<quanstro@labs.coraid.com> wrote:
>> > 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 ';'?
>
> i don't use hoc very often. =A0i tend to use acid. =A0(!)
> 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.
>

I normally use acid for interactive use, but for scripts bc is great,
supports hex,
has C like syntax, can do floating point and it has a big precision.
--=20
- curiosity sKilled the cat