From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] FORTRAN
Date: Tue, 20 Mar 2018 14:27:39 -0600 [thread overview]
Message-ID: <CANCZdfpnvqjZAgYXGHVk2koHEUWLEyErs=iM-YUDx4ez6UpJzw@mail.gmail.com> (raw)
In-Reply-To: <CABH=_VSjLP1XRVa6MG-q_nCyNRMqF8iKSrt8o5Tu-e+615zDMQ@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
On Tue, Mar 20, 2018 at 2:21 PM, Paul Winalski <paul.winalski at gmail.com>
wrote:
> On 3/20/18, Ron Natalie <ron at ronnatalie.com> wrote:
> > Having worked on system programming for UNIX and a few of the PDP-11 DEC
> > OS’s (DOS, RT, RSX, and in passing RSTS), I can tell you Fortran was
> > abhorrent.
> >
> Yes, Fortran is as awful for system programming as C is for numeric
> programming that involves throwing multidimensional arrays around.
> Screwdrivers always make bad hammers.
>
With care, and the right additional pseudo-primitives, you can do quite
interesting systems-programming-like things in Fortran. But they are
usually a variation on RATFOR and often involve more pain than would
otherwise have been needed, but it's possible. I once did some low-level
systems stuff in FORTRAN-66 that lived under a psuedo Fortran 77
pre-processor that had some CPP-like macro features....
And I will never, ever, do it again :). I might do Turbo-PASCAL again, but
no system's programming in Fortran.
Warner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180320/9d76599d/attachment.html>
next prev parent reply other threads:[~2018-03-20 20:27 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 21:52 [TUHS] RIP John Backus 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 [this message]
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
2018-03-19 14:26 ` Warner Losh
2018-03-21 14:51 [TUHS] FORTRAN Noel Chiappa
2018-03-21 21:57 ` Charles Anthony
[not found] <mailman.48.1521640130.3788.tuhs@minnie.tuhs.org>
2018-03-21 22:58 ` Johnny Billquist
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='CANCZdfpnvqjZAgYXGHVk2koHEUWLEyErs=iM-YUDx4ez6UpJzw@mail.gmail.com' \
--to=imp@bsdimp.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).