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>
Date: Thu, 13 May 2010 11:51:30 +0400
MIME-Version: 1.0
From: Alexander Sychev <santucco@gmail.com>
Message-ID: <op.vcmv3401hipq0d@santucco.avp.ru>
In-Reply-To: <AANLkTin7F2mT7yhs4VQATcvoIsKMDjsYwDzQX2sN6zyV@mail.gmail.com>
User-Agent: Opera Mail/10.10 (Linux)
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] hoc output format
Topicbox-Message-UUID: 1fc2e568-ead6-11e9-9d60-3106f5b1d025

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 calculation
tasks, not for  processing input files with a data.

On Wed, 12 May 2010 22:06:20 +0400, Akshat Kumar =20
<akumar@mail.nanosouffle.net> wrote:

> I've found that awk(1) is more useful
> (rather, more powerful) for doing
> programmed computations (number
> crunching, etc.), where hoc(1) is
> more of a convenience for basic
> calculations.
>
>
> Best,
> ak
>
> On Wed, May 12, 2010 at 3:41 AM, Alexander Sychev <santucco@gmail.com> =
=20
> wrote:
>> Hello!
>>
>> IFAIK, hoc(1) hasn't got such possibility.
>> awk(1) can help:
>>
>> $ hoc -e PI | awk '{printf "%2.2f", $0}'
>> 3.14
>>
>> On Wed, 12 May 2010 14:24:57 +0400, Rudolf Sykora =20
>> <rudolf.sykora@gmail.com>
>> wrote:
>>
>>> Hello everyone,
>>>
>>> is there any way to control the output format of hoc(1), i.e. e.g. th=
e
>>> number of decimal places printed?
>>>
>>> Thanks
>>> Ruda
>>
>>
>> --
>> Best regards,
>>  santucco
>>
>>


--=20
Best regards,
   santucco