From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] Etymology of bc(1)
Date: Fri, 12 Sep 2014 11:03:03 +1000 (EST) [thread overview]
Message-ID: <alpine.BSF.2.00.1409121055300.63870@aneurin.horsfall.org> (raw)
In-Reply-To: <20140911221742.GJ23708@mercury.ccil.org>
On Thu, 11 Sep 2014, John Cowan wrote:
> > I've heard "binary" because it used binary arithmetic (and limited
> > precision), and "basic" because it was a lot simpler than "dc" (which
> > I've always thought was "decimal" calculator due to it using arbitrary
> > precision decimal arithmetic).
>
> That can't be right. Bc was just an overlay to dc that parsed bc
> language, compiled it into dc language, and fed dc from a pipe (all the
> output was direct from dc). So the arithmetic capabilities were exactly
> the same.
Hey, I never made any claim as to its veracity, and I lost my old manuals
in a house move.
On the *nix systems to which I have access, bc(1) is a standalone
program on FreeBSD and OSX, but pipes to dc(1) on OpenBSD. I cannot
check my Penguin box (Ubuntu) because its keyboard died, and I didn't
set up remote access to it.
All boxen say "arbitrary-precision arithmetic language and calculator" or
variants thereof.
-- Dave
next prev parent reply other threads:[~2014-09-12 1:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 21:24 Christian Neukirchen
2014-09-11 21:41 ` Warner Losh
2014-09-11 22:04 ` Dave Horsfall
2014-09-11 22:17 ` John Cowan
2014-09-11 23:34 ` scj
2014-09-12 1:03 ` Dave Horsfall [this message]
2014-09-12 13:37 ` random832
2014-09-12 14:18 ` Steve Nickolas
2014-09-12 20:02 ` Dave Horsfall
2014-09-12 1:54 Noel Chiappa
2014-09-12 2:35 ` Mark Longridge
2014-09-12 6:00 ` Dave Horsfall
2014-09-12 11:15 ` John Cowan
2014-09-12 11:36 ` Otto Moerbeek
2014-09-12 17:12 ` scj
2014-09-12 17:18 ` Warner Losh
2014-09-12 19:02 ` Clem Cole
2014-09-12 19:36 ` Dave Horsfall
2014-09-12 20:03 ` Warner Losh
2014-09-12 19:32 ` Dave Horsfall
2014-09-12 18:28 ` Tim Bradshaw
2014-09-13 2:52 ` Dave Horsfall
2014-09-12 3:15 Noel Chiappa
2014-09-12 3:33 ` Larry McVoy
2014-09-12 6:10 ` Dave Horsfall
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=alpine.BSF.2.00.1409121055300.63870@aneurin.horsfall.org \
--to=dave@horsfall.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).