From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] hoc output format
Date: Thu, 13 May 2010 16:04:41 +0100 [thread overview]
Message-ID: <5B5AFBEB-D6BD-4218-89B3-CB7EA05C1AAB@fastmail.fm> (raw)
In-Reply-To: <84f53dabe8357c852216d6c9024f6eb0@coraid.com>
On 13 May 2010, at 15:23, erik quanstrom wrote:
>>> 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.
Acid is nicer than dc or bc for this? I don't do much in the way of
programming calculations at present and usually resort to dc to do
them. Anything more convenient would be appreciated. :)
As for hoc, I'm mostly doing floating-point work where presentation is
irrelevant, so it's quite useful for me, but too often I find myself
preferring to use one of those silly graphical calculator applications
just to cut down on the visual noise.
--
Simplicity does not precede complexity, but follows it. -- Alan Perlis
next prev parent reply other threads:[~2010-05-13 15:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 10:24 Rudolf Sykora
2010-05-12 10:41 ` Alexander Sychev
2010-05-12 18:06 ` Akshat Kumar
2010-05-13 7:51 ` Alexander Sychev
2010-05-13 13:24 ` erik quanstrom
2010-05-13 14:06 ` Alexander Sychev
2010-05-13 14:23 ` erik quanstrom
2010-05-13 15:04 ` Ethan Grammatikidis [this message]
2010-05-13 15:09 ` Gorka Guardiola
2010-05-13 15:37 ` erik quanstrom
2010-05-13 15:16 ` roger peppe
2010-05-13 15:31 ` erik quanstrom
2010-05-13 15:53 ` roger peppe
2010-05-13 16:06 ` erik quanstrom
2010-05-13 16:16 ` roger peppe
2010-05-13 15:54 ` Ethan Grammatikidis
2010-05-13 16:08 ` roger peppe
2010-05-13 15:20 ` Rudolf Sykora
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5B5AFBEB-D6BD-4218-89B3-CB7EA05C1AAB@fastmail.fm \
--to=eekee57@fastmail.fm \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).