From: tih at hamartun.priv.no (Tom Ivar Helbekkmo)
Subject: [COFF] The Elements Of Style: UNIX As Literature
Date: Wed, 11 Nov 2020 13:21:10 +0100 [thread overview]
Message-ID: <m2v9ecdqyx.fsf@thuvia.hamartun.priv.no> (raw)
In-Reply-To: <20201111083156.GA57519@server.rulingia.com> (Peter Jeremy via COFF's message of "Wed, 11 Nov 2020 19:31:56 +1100")
Peter Jeremy via COFF <coff at minnie.tuhs.org> writes:
> Since no-one has mentioned it, the reason why Fortran and Cobol ignore
> columns 73-80 goes back to the IBM 711 card reader - which could read any
> (but usually configured for the first) 72 columns into pairs of 36-bit words
> in an IBM 701.
...and for those who, like me, did a double-take on that, thinking "WTF?
That would mean it read *rows* of bits from the card into machine words!",
I checked, and yes, that's exactly what it did.
https://en.wikipedia.org/wiki/Punched_card_input/output#Binary_format
-tih (who learned FORTRAN using punched cards on a UNIVAC)
--
Most people who graduate with CS degrees don't understand the significance
of Lisp. Lisp is the most important idea in computer science. --Alan Kay
next prev parent reply other threads:[~2020-11-11 12:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEuQd1AWs=jpHYk3nGpKsBV=qF4DZVXvXzynSeDK5S-r-hfryw@mail.gmail.com>
[not found] ` <20201106014109.GP26296@mcvoy.com>
[not found] ` <CAD2gp_Q-wTvG2cAW5goJFYW3A6qF9zOuTh=Y4Kahh0nLBtof2Q@mail.gmail.com>
[not found] ` <20201106063725.GB99027@eureka.lemis.com>
[not found] ` <5BE1CBD5-C9EB-45D4-B135-E58BCCCBE38C@gmail.com>
[not found] ` <3c54b19d-e604-68eb-2b4b-0b65e9cfb896@earthlink.net>
2020-11-06 17:56 ` [COFF] [TUHS] " clemc
[not found] ` <20201106150609.GR26296@mcvoy.com>
[not found] ` <CALMnNGg=9KHCwqaqdFESBQr=Ru_qzM=x-S2fc=ewgJNf2zLRFQ@mail.gmail.com>
[not found] ` <20201106222302.GG26411@mcvoy.com>
2020-11-07 0:16 ` dave
[not found] ` <CAKzdPgx1Ptu=sahO3o5KYS-A=vnfXK-hs=QeVwO_Vd1cFfaeqw@mail.gmail.com>
[not found] ` <a588c934-e403-2a4e-4701-669b8c14e989@gmail.com>
[not found] ` <CAC20D2PPw3Ua3-VpMYjh=NaC09=9Q528kqEvE7SvmO3Ly2JO0A@mail.gmail.com>
[not found] ` <175409f6-af94-601e-3db3-a5af5d7f64d0@gmail.com>
2020-11-06 15:53 ` clemc
2020-11-06 19:22 ` tytso
2020-11-06 19:24 ` clemc
2020-11-06 22:58 ` grog
2020-11-07 21:04 ` clemc
2020-11-07 23:05 ` dave
2020-11-09 4:36 ` [COFF] Daisy wheel printers (was: [TUHS] The Elements Of Style: UNIX As Literature) grog
2020-11-09 14:26 ` clemc
2020-11-10 0:10 ` grog
2020-11-10 14:48 ` clemc
2020-11-10 15:10 ` stewart
2020-11-09 22:08 ` dave
2020-11-10 0:48 ` grog
[not found] ` <202011061546.0A6Fkv3D034443@elf.torek.net>
2020-11-06 16:22 ` [COFF] [TUHS] The Elements Of Style: UNIX As Literature clemc
2020-11-06 18:12 ` torek
2020-11-07 2:52 ` cym224
[not found] ` <20201106225422.GD99027@eureka.lemis.com>
[not found] ` <20201106232901.AkY2I%steffen@sdaoden.eu>
2020-11-07 4:22 ` grog
2020-11-07 20:31 ` steffen
2020-11-11 8:31 ` [COFF] " peter
2020-11-11 12:21 ` tih [this message]
2020-11-11 21:09 ` dave
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=m2v9ecdqyx.fsf@thuvia.hamartun.priv.no \
--to=coff@minnie.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).