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:54:32 +0100 [thread overview]
Message-ID: <34C68D51-B2FF-4D3A-B4A0-C4B539CAD060@fastmail.fm> (raw)
In-Reply-To: <AANLkTimWkzrs6J-0G_ESGMqeYj1P1FRrMR6lq7GpdM3P@mail.gmail.com>
On 13 May 2010, at 16:16, roger peppe wrote:
> On 13 May 2010 15:23, erik quanstrom <quanstro@labs.coraid.com> wrote:
>> i typically do programming calculations and floating point
>> just isn't the right way to do that.
>
> it's ok if you stick to 32 bit and don't do divisions.
>
> personally for off-the-cuff command-line calculations
> i've been using my own "fc" for years and
> years. nothing else quite hits the spot, but
> i'm biased.
>
> my reasons: hoc doesn't do bit level ops, has too much syntax that
> needs
> quoting, and if you're quoting, it's awkward (in rc) to insert
> environment variables inside the quotes. dc
> doesn't take command line arguments,
> doesn't do floating point and its output isn't suitable
> for as input.
what do you mean by "its output isn't suitable for use as input"? i'm
just curious, have never used it that way. hum... having asked that
question i tried some operations producing very lare numbers and they
started to be printed with backslash-newlines in them. not nice, but
such a form is suitable for input back to dc.
>
> there's a man page for the inferno version of fc here,
> in case anyone's interested:
> http://www.vitanuova.com/inferno/man/1/fc.html
>
fc does look good for strictly command line use (scripts, perhaps?) i
usually want to fire up a calculator in a window of its own & refer to
it as needed.
--
Simplicity does not precede complexity, but follows it. -- Alan Perlis
next prev parent reply other threads:[~2010-05-13 15:54 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
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 [this message]
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=34C68D51-B2FF-4D3A-B4A0-C4B539CAD060@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).