Computer Old Farts Forum
 help / color / mirror / Atom feed
From: clemc at ccc.com (Clem Cole)
Subject: [COFF] Happy birthday, John Backus!
Date: Thu, 5 Dec 2019 15:56:07 -0500	[thread overview]
Message-ID: <CAC20D2M6gKfMX=AtQhHpHwCUYWsWSXVhp516BGFABE5rZp7wOA@mail.gmail.com> (raw)
In-Reply-To: <m2muc6sg9x.fsf@thuvia.hamartun.priv.no>

Tom - this all makes perfect sense.  Very cool.  You are undoubtedly the
source!!!   I'm sure I must have gotten it from you, but I admit that I
>>had<< thought I had seen it elsewhere, earlier before Dave had retired
(which was a few years back before Intel moved the team from NH to MA).
That's why I asked had you posted to somewhere else earlier maybe?

FWIW: Google translates the intro para to be:  which is similar to your
translation.  You rewrote ND-10... to Norsk Data which makes complete sense
by making the code more understandable out of the context of the document.

The FORTRAN program below can be compiled and executed on an ND-10/100 FTN
compiler. It consists only of FORTRAN reserved words and 'contains only one
numeric constant (it is in a text string). The program produces a known
mathematical "figure".

The program is an example that even FORTRAN is a block structured language.

I note the original as the PROGRAM card is by itself, but not indented.
Which is somewhat consistent with the Dave's observation of F4 requiring
PROGRAM, END and STOP to be on seperate card.

BTW:  given today's exchange, I sent the compiler team a note to state, we
got it from you and I've asked them to add a pointer to this document your
provided also.

Thanks again,
Clem



On Thu, Dec 5, 2019 at 2:50 PM Tom Ivar Helbekkmo <tih at hamartun.priv.no>
wrote:

> Clem Cole <clemc at ccc.com> writes:
>
> > I suspect when this was sent out to wherever I picked it up a few
> > years ago, the code had been changed to be 'pure F4' ;-)
>
> The version I have is the one that was floating around the SINTRAN
> environment at the Norwegian Institute of Technology when I was there
> back in the eighties.  I don't know where it originally came from, but
> it was printed in the in-house information publication RUN-NYTT in 1982.
>
> It's on page 9 of this issue:
>
>
> https://folk.ntnu.no/klv/IT-historie-ntnu/Run-nytt-1977-93/run-nytt-1-1982.pdf
>
> The comment at the top of the version you posted is actually my own
> translation of the text introducing the printed program text.
>
> -tih
> --
> 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 part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20191205/84c303aa/attachment.html>


  reply	other threads:[~2019-12-05 20:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03  7:55 dave
2019-12-03 13:44 ` clemc
2019-12-03 15:57   ` toby
2019-12-03 16:05     ` lars
2019-12-04  5:41   ` wobblygong
2019-12-04 14:54     ` clemc
2019-12-04 15:08       ` clemc
2019-12-04 15:14     ` clemc
2019-12-05  6:11       ` wobblygong
2019-12-05 12:38         ` clemc
2019-12-05 17:03   ` tih
2019-12-05 18:44     ` clemc
2019-12-05 19:03       ` clemc
2019-12-05 19:50         ` tih
2019-12-05 20:56           ` clemc [this message]
2019-12-03 19:20 ` cym224

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='CAC20D2M6gKfMX=AtQhHpHwCUYWsWSXVhp516BGFABE5rZp7wOA@mail.gmail.com' \
    --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).