The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: scj@yaccman.com (scj@yaccman.com)
Subject: [TUHS] terminal - just for fun
Date: Mon, 4 Aug 2014 11:04:39 -0700	[thread overview]
Message-ID: <a2660c1c487bcd938c343c49f017bbf8.squirrel@webmail.yaccman.com> (raw)
In-Reply-To: <20140802034551.GA30208@eureka.lemis.com>

Remember that writing programs on terminals was a relative latecomer --
FORTRAN was designed for punched cards.  Their 6-bit character set has
"numbers" and "letters" (no case need apply).  The printers and other
supporting peripherals printed capital letters, probably because you could
get legibility with fewer dots that way and didn't have to worry about
descenders.

At Bell Labs (before Unix days) programmers wrote their programs on coding
sheets and handed them in to a room full of keypunchers.  They would punch
the program up on cards, and then a second person would repeat the process
using a verifier, a piece of hardware that took in a punched card, and had
a keyboard, and would verify that what the person typed in was what had
been punched on the card.  Then the punched and verified deck of cards was
returned to the programmer, who could submit it to the mainframe to run
it.

Although the coding sheet had little tick marks to indicate the column
positions, the keypunchers took advantage of FORTRAN syntax to simply
ignore spaces (they did know enough to respect blanks in Hollerith strings
and to start typing the program in the appropriate column).  Leaving the
blanks out not only made the process go faster, but also reduced the
number of false failures in verification, where the original keypuncher
and verifier disagreed on how many spaces should be inserted.

The model 33 Teletypes that were the most common terminal attached to Unix
in the early days had only a single case, as I recall, being primarily
used with paper tape with a character set closely related to the character
set used on punched cards (although with some features that eventually
become supported in ASCII).  Unix, however, interpreted the "letters" in
the character set as lower case by default, which was highly unusual at
that time, since there were almost no printers or terminals that would
print upper and lower case.


> On Saturday,  2 August 2014 at  4:27:50 +0100, Tim Bradshaw wrote:
>>
>> On 2 Aug 2014, at 02:49, Dave Horsfall <dave at horsfall.org> wrote:
>
>> Did FORTRAN understand lowercase, always?
>
> No.  It was first implemented on the IBM 704, which had a 6 bit BCD
> character set.  No lower case.
>





  parent reply	other threads:[~2014-08-04 18:04 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31 19:44 Tim Newsham
2014-07-31 22:59 ` Dave Horsfall
2014-08-02 13:30   ` random832
2014-08-01  9:00 ` Dario Niedermann
2014-08-01 15:13   ` Andy Kosela
2014-08-01 15:28     ` Milo Velimirović
2014-08-01 17:50       ` Mary Ann Horton
2014-08-01 17:59         ` Cory Smelosky
2014-08-01 19:59           ` Tim Newsham
2014-08-01 20:11         ` Dave Horsfall
2014-08-01 20:35           ` John Cowan
2014-08-02  1:49             ` Dave Horsfall
2014-08-02  3:27               ` Tim Bradshaw
2014-08-02  3:45                 ` Greg 'groggy' Lehey
2014-08-02  9:24                   ` Tim Bradshaw
2014-08-02 14:28                     ` [TUHS] Lisp is a family quarrel John Cowan
2014-08-03  6:47                   ` [TUHS] terminal - just for fun Dave Horsfall
2014-08-04 18:04                   ` scj [this message]
2014-08-04 18:18                     ` Tim Newsham
2014-08-04 18:29                       ` John Cowan
2014-08-04 19:10                         ` Tim Newsham
2014-08-04 19:13                           ` Milo Velimirović
2014-08-04 19:21                             ` Tim Newsham
2014-08-04 18:28                     ` John Cowan
2014-08-05 13:13                       ` arnold
2014-08-05 14:20                         ` John Cowan
2014-08-05 14:46                           ` arnold
2014-08-04 20:15                     ` Jaap Akkerhuis
2014-08-04 20:39                       ` Dave Horsfall
2014-08-02  4:28                 ` Dave Horsfall
2014-08-02  4:46                 ` Warner Losh
2014-08-02 13:22                 ` Nemo
2014-08-02  3:37               ` Greg 'groggy' Lehey
2014-08-02  5:45                 ` Dave Horsfall
2014-08-02  6:09                   ` Greg 'groggy' Lehey
     [not found]               ` <20140802061214.GC13625@mercury.ccil.org>
2014-08-02  6:17                 ` Dave Horsfall
2014-08-02 13:35                   ` Bill Pechter
2014-08-02 14:04                     ` Milo Velimirovic
2014-08-03  2:00                       ` Greg 'groggy' Lehey
2014-08-02 14:30                   ` John Cowan
2014-08-01 21:32           ` Dario Niedermann
2014-08-01 21:38             ` Warner Losh
2014-08-01 21:56               ` Dario Niedermann
2014-08-04 19:46 Doug McIlroy
2014-08-04 20:46 Norman Wilson
2014-08-04 21:07 ` Diomidis Spinellis
2014-08-06  2:56 Doug McIlroy
2014-08-06  6:45 ` arnold
2014-08-06  7:47   ` Dave Horsfall
2014-08-06  9:09     ` Jaap Akkerhuis
2014-08-06 20:43     ` Ronald Natalie
2014-08-06 21:40       ` Mary Ann Horton
2014-08-06 13:22   ` John Cowan
2014-08-06 13:44     ` Steve Nickolas
2014-08-06 15:26     ` Jeremy C. Reed
2014-08-06 16:15       ` Armando Stettner
2014-08-06 20:16         ` Jaap Akkerhuis
2014-08-06 20:32           ` Ronald Natalie
2014-08-06 16:37       ` John Cowan
2014-08-06 17:53         ` scj
2014-08-06 19:44           ` A. P. Garcia
2014-08-06 20:36             ` Ronald Natalie
2014-08-06 20:38           ` Ronald Natalie
2014-08-06 16:49       ` Milo Velimirović
2014-08-06 18:26       ` Mary Ann Horton
2014-08-06 18:48         ` Mary Ann Horton

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=a2660c1c487bcd938c343c49f017bbf8.squirrel@webmail.yaccman.com \
    --to=scj@yaccman.com \
    /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).