From: clemc at ccc.com (Clem Cole)
Subject: [COFF] How much Fortran?
Date: Mon, 3 Feb 2020 11:20:53 -0500 [thread overview]
Message-ID: <CAC20D2OxDH5W1A2+Ntuz1CiNn_R07suLoow2OOK+-BXRy8e7hA@mail.gmail.com> (raw)
In-Reply-To: <20200203160643.GO3216@mcvoy.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
On Mon, Feb 3, 2020 at 11:06 AM Larry McVoy <lm at mcvoy.com> wrote:
> But in the CS department and then later at Sun, everything I came
> in contact with was in C. So in my world it wasn't a thing.
>
Mine either mind you, but ... like me, Sun sold a >>lot<< of high-end
systems to run Fortran codes. Like Masscomp, both firms compiler groups
had to ensure that our Fortran compilers were not just F77, but VMS FORTRAN
compliant - because when UNIX hit the scene, VMS FORTRAN was the *Lingua
Franca* of the users (but just not us system folks).
I always like to know what is paying the bills 😎
>
> Modern Fortran is apparently a lot more pleasant than what I learned.
Without a doubt, but I'd still rather not program in it.😂 I just want to
make sure it works and runs really fast, so our customers want to use a
large number of our high-end chips and keep that robot in AZ that is
turning silicon into gold.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200203/ebabc3d6/attachment-0001.html>
next prev parent reply other threads:[~2020-02-03 16:20 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 [this message]
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
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=CAC20D2OxDH5W1A2+Ntuz1CiNn_R07suLoow2OOK+-BXRy8e7hA@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).