From: Ralph Corderoy <ralph@inputplus.co.uk>
To: tuhs@tuhs.org
Subject: [TUHS] Re: A second Unix Patent
Date: Sat, 04 Mar 2023 09:22:16 +0000 [thread overview]
Message-ID: <20230304092216.287E22020E@orac.inputplus.co.uk> (raw)
In-Reply-To: <20230304015746.DD95518C08D@mercury.lcs.mit.edu>
Hi,
Noel wrote:
> I fed '26 3 ^p' into 'dc' to see just how big it was - and got
> "17576", a 16-bit word array of which would fit into a PDP-11 64KB
> address space.
I'm a fan of dc(1), but also of units(1) and since both seem underused
here's an alternative method.
$ units -1v '26^3 16 bit' 64KiB
26^3 16 bit = 0.53637695 * 64KiB
--
Cheers, Ralph.
next prev parent reply other threads:[~2023-03-04 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 1:57 Noel Chiappa
2023-03-04 9:22 ` Ralph Corderoy [this message]
2023-03-04 15:08 ` Clem Cole
-- strict thread matches above, loose matches on Subject: below --
2023-03-01 22:59 [TUHS] " Warner Losh
2023-03-02 4:41 ` [TUHS] " Douglas McIlroy
2023-03-02 5:16 ` David Arnold
2023-03-03 13:29 ` Steve Mynott
2023-03-03 19:19 ` James Frew
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=20230304092216.287E22020E@orac.inputplus.co.uk \
--to=ralph@inputplus.co.uk \
--cc=tuhs@tuhs.org \
/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).