Computer Old Farts Forum
 help / color / mirror / Atom feed
From: crossd at gmail.com (Dan Cross)
Subject: [COFF] How much Fortran?
Date: Mon, 3 Feb 2020 12:06:26 -0500	[thread overview]
Message-ID: <CAEoi9W79Cx9tupSgGBLtdSoNTuDj22+0Dw-Khu6vu48Y7kLn-A@mail.gmail.com> (raw)
In-Reply-To: <acbac8c4-fb0f-4419-bb22-2349493b2236@kilonet.net>

On Sun, Feb 2, 2020 at 8:46 PM Arthur Krewat <krewat at kilonet.net> wrote:

> So, given the membership here, I wonder, does anyone have the inside
> scoop? How much Fortran was used ?
>
>
> https://science.slashdot.org/story/20/01/31/1837209/nasa-is-trying-to-save-voyager-2-after-a-power-glitch-shut-down-its-instruments


I have this memory, but I cannot verify it.

When I first joined the ACM, I got to select what SIGs I wanted to
(sub?)join. SIGPLAN seemed interesting because, hey, programming languages
are kind of cool, so I joined it. At the time, they distributed a
newsletter called, I think, the "Fortran Forum"; perhaps that was even a
subgroup inside of SIGPLAN.

I only remember getting one or two issues of the newsletter. But I believe
one of them had an article about Voyager and the use of Fortran. The
article stuck out to me because it mentioned that they thought the mission
would only has for (however long), but of course it's been going on much
longer than originally anticipated. However, I can find no reference to
that now, and perhaps the article I'm recalling wasn't talking about either
Fortran (forth as an alternative?) or a mission other than Voyager.

Regardless, one DOES wonder in what capacity FORTRAN was used in the
mission. Was it used on the onboard computers, or was it used on the
downlink stations for e.g. data analysis?

        - Dan C.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200203/82861db6/attachment.html>


  parent reply	other threads:[~2020-02-03 17:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03  1:38 krewat
2020-02-03  3:47 ` lm
2020-02-03 15:53   ` clemc
2020-02-03 16:06     ` lm
2020-02-03 16:20       ` clemc
2020-02-03 19:50     ` dave
2020-02-03 17:01   ` thomas.paulsen
2020-02-03  4:50 ` drb
2020-02-03 17:06 ` crossd [this message]
2020-02-03 18:36   ` 
2020-02-03 19:26     ` cym224
2020-02-04  1:25     ` wobblygong
2020-02-06  4:59 rudi.j.blom
2020-02-06 20:04 ` dave
2020-02-07 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=CAEoi9W79Cx9tupSgGBLtdSoNTuDj22+0Dw-Khu6vu48Y7kLn-A@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).