The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@iitbombay.org>
To: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: Does anybody know the etymology of the term "word" as in collection of bits?
Date: Sun, 11 Sep 2022 08:30:25 -0700	[thread overview]
Message-ID: <45A8556C-CAFE-420A-8571-974B9D67D436@iitbombay.org> (raw)
In-Reply-To: <CAKH6PiVMydVmrU2iTpEuDwKqgemmdm22ope7kx2UNOCHswawPA@mail.gmail.com>

On Sep 11, 2022, at 6:30 AM, Douglas McIlroy <douglas.mcilroy@dartmouth.edu> wrote:
> 
> [Algol 68's presupposition is visible in declarations like "long long
> long ... int". An implementation need support only a limited number of
> "longs", but each supported variety must have a definite maximum
> value, which is returned by an "environment enquiry" function. For
> amusement, consider the natural idea of implementing the longest
> variety with bignums.]

It would be natural to use a Kleene star to represent an arbitrarily
long string of LONGs -- "long* int" -- though AFAIK Algol68 doesn't
do bignums. Weirdly even most 21st century progamming languages do
not provide built-in support for bignums!

C's INT_MAX, LONG_MAX etc are kind of an environment enquiry...

  parent reply	other threads:[~2022-09-11 15:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-11 13:30 Douglas McIlroy
2022-09-11 15:08 ` John Cowan
2022-09-11 15:30 ` Bakul Shah [this message]
2022-09-11 15:45   ` Paul Winalski
2022-09-11 16:20     ` Steve Nickolas
  -- strict thread matches above, loose matches on Subject: below --
2022-09-09 19:39 Nelson H. F. Beebe
2022-09-09 20:27 ` Bakul Shah
2022-09-09 21:12   ` Henry Bent
2022-09-09 21:44   ` Dave Horsfall
2022-09-09 18:46 Norman Wilson
2022-09-10  1:35 ` Paul Winalski
2022-09-09 17:26 Douglas McIlroy
2022-09-09  1:33 Douglas McIlroy
2022-09-09  2:12 ` Larry McVoy
2022-09-13 14:23   ` John Foust via TUHS
2022-09-09  2:45 ` George Michaelson
2022-09-16  5:55 ` Marc Donner
2022-09-08 21:16 Noel Chiappa
2022-09-08 21:24 ` Dan Halbert
2022-09-08 18:20 Noel Chiappa
2022-09-08 19:28 ` Jim Capp
2022-09-08 16:51 [TUHS] " Jon Steinhart
2022-09-08 16:56 ` [TUHS] " Andrew Hume
2022-09-08 17:28 ` Dan Halbert
2022-09-09  0:00   ` Greg 'groggy' Lehey
2022-09-09 15:49     ` Paul Winalski
2022-09-09 18:44       ` Bakul Shah

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=45A8556C-CAFE-420A-8571-974B9D67D436@iitbombay.org \
    --to=bakul@iitbombay.org \
    --cc=douglas.mcilroy@dartmouth.edu \
    --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).