The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: scj@yaccman.com (Steve Johnson)
Subject: [TUHS] RIP John Backus
Date: Sun, 18 Mar 2018 17:26:36 -0700	[thread overview]
Message-ID: <52c5a2e1a53e5a0d88246bf29e52acf696e9c85a@webmail.yaccman.com> (raw)
In-Reply-To: <CABH=_VSEyOwDPr0wtnn2cQZ1tCQU+v_R4pBEg=-VeQVUxu6Jhw@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2642 bytes --]

I had an interesting run-in with FORTRAN's blank treatment very early
in my career.   A couple of weeks after I graduated from college I
had a summer job at Bell Labs.  I was given a job to program a state
minimization algorithm -- they expected it to take me the whole
summer.  A couple of days after arriving, i heard about a new
language, SNOBOL, developed at another location at Bell Labs.  This
sounded like the perfect language to write my program in, so I got a
copy to use (I think I was the first user at Murray Hill).

Now, in those days, there were rooms full of "keypunch girls" (sic)
whose job was to punch up our programs (written on coding sheets) and
verify them and give us the deck back.  The vast majority of jobs
they encountered were FORTRAN, and to avoid ambiguity they simply
skipped all blanks.   (it wasn't quite that easy -- they knew about
column 7 and hollerith strings).  But any blanks that we wanted on
the cards had to be explicitly indicated on the coding sheet.

Of course, SNOBOL had what we would consider now a more modern syntax
with blanks significant and nothing magic about columns 6 or 7...   
So when I gave them my first 2-page SNOBOL program, they typed
everything on each line starting in column 7 and with all blanks
removed.    For some reason, the first couple of cards looked OK to
me, so I submitted the deck, and proceeded to get a thick printout
that I think enumerated every error message the compiler could
produce.

I started indicating my blanks carefully but their habit persisted,
and almost any nontrivial job  I gave them had errors, either because
I hadn't inidicated a blank or they hadn't typed it when I indicated
it.

Since I had been punching cards myself for a couple of years at
college, and when working 2nd shift (when turnaround was much better)
there were no keypunchers available, after a couple of weeks I got
them to agree to let me keypunch my own programs.  A few years later,
the keypunchers were gone, having been rendered obsolete by time
sharing and online editing...

Oh, and I got the job done in 3 weeks once I got SNOBOL to work...  
It really was the right language for the job...

Steve

PS:  For years afterwards, when I punched in FORTRAN programs I left
out all the blanks.  It wasn't until  I worked on a large program
with several other people that I was forced to change this habit, my
coworkers having threatened me with death or dismemberment if I
didn't... 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180318/2a26a542/attachment.html>


  parent reply	other threads:[~2018-03-19  0:26 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16 21:52 Dave Horsfall
2018-03-16 23:42 ` Dan Stromberg
2018-03-17  0:08   ` Dave Horsfall
2018-03-17  0:26     ` Arthur Krewat
2018-03-17  0:36       ` Dave Horsfall
2018-03-17  1:40       ` Charles H Sauer
2018-03-17  1:57 ` Nemo
2018-03-17  7:20 ` Bakul Shah
2018-03-17 13:43 ` Clem Cole
2018-03-17 17:06   ` Steve Simon
2018-03-17 19:15     ` Pierre DAVID
2018-03-17 19:41       ` Charles Anthony
2018-03-18 11:02       ` Steve Simon
2018-03-17 19:22   ` Tim Bradshaw
2018-03-17 19:28   ` Mike Markowski
2018-03-18 18:51 ` Paul Winalski
2018-03-18 21:07   ` Clem Cole
2018-03-19 14:50     ` Dan Cross
2018-03-19 15:43       ` Clem Cole
2018-03-19 15:46         ` Clem Cole
2018-03-19 17:39           ` Paul Winalski
2018-03-19 17:43             ` George Michaelson
2018-03-19 18:16               ` Steve Nickolas
2018-03-19 17:48             ` Clem Cole
2018-03-19 17:59               ` Jon Forrest
2018-03-19 18:40                 ` Tom Ivar Helbekkmo
2018-03-19 19:40                   ` Arthur Krewat
2018-03-19 15:55       ` Clem Cole
2018-03-19 16:58         ` [TUHS] FORTRAN Steve Johnson
2018-03-19 17:32           ` Jon Forrest
2018-03-20 17:42             ` Paul Winalski
2018-03-20 17:47               ` George Michaelson
2018-03-19 18:47           ` Larry McVoy
2018-03-20 18:15           ` Dan Cross
2018-03-20 19:55             ` Ron Natalie
2018-03-20 20:21               ` Paul Winalski
2018-03-20 20:27                 ` Warner Losh
2018-03-21  8:10                 ` Peter Jeremy
2018-03-21 20:56                   ` Ron Natalie
2018-03-21 21:15                 ` Dennis Boone
2018-03-20 21:36               ` Clem Cole
2018-03-20 21:59                 ` Ron Natalie
2018-03-20 23:00                 ` Bakul Shah
2018-03-21 13:48                 ` Paul Winalski
2018-03-21 20:55                   ` Ron Natalie
2018-03-18 21:26   ` [TUHS] RIP John Backus Tim Bradshaw
2018-03-19  0:26   ` Steve Johnson [this message]
2018-03-19 14:26     ` Warner Losh
     [not found] <mailman.17.1521243734.3788.tuhs@minnie.tuhs.org>
2018-03-17 14:47 ` Paul McJones
2018-03-17 15:54   ` Dave Horsfall
     [not found] <mailman.19.1521302091.3788.tuhs@minnie.tuhs.org>
2018-03-17 17:49 ` Paul McJones
2018-03-17 18:52   ` Arthur Krewat
2018-03-18  3:39     ` Greg 'groggy' Lehey
2018-03-18  7:35     ` Otto Moerbeek
     [not found] <mailman.21.1521314548.3788.tuhs@minnie.tuhs.org>
2018-03-17 20:01 ` Paul McJones
2018-03-17 20:14 ` Paul McJones
2018-03-17 22:27   ` Steve Johnson
2018-03-18 13:33 Noel Chiappa

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=52c5a2e1a53e5a0d88246bf29e52acf696e9c85a@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).