The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] FORTRAN
Date: Tue, 20 Mar 2018 17:36:16 -0400	[thread overview]
Message-ID: <CAC20D2NNxp-3Qpw1=_3+3ZT6pk-b_answ88-KLZCw7j3gf7WOw@mail.gmail.com> (raw)
In-Reply-To: <002f01d3c085$6b5a26d0$420e7470$@ronnatalie.com>

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

On Tue, Mar 20, 2018 at 3:55 PM, 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.
>
> Sure it was the only high-level language I had on the RT and RSX systems,
>
​And that was the problem... DEC did not market good tools besides
assembler and FTN for RT and RSX.   3rd parties like Oregon SW and
Whitesmiths' eventually produced good Pascal and C implementation
respectfully.   But, like you, most people I knew, and in my own
experience; nothing but asm and FTN was there.

Paul can correct me, but I don't think DEC even developed a Pascal for TOPS
originally - IIRC the one I used came from the universities.   I think the
first Pascal sold was targeted for the VAX.  Also, RT11 and RSX were
'laboratory' systems and those systems were dominated by Fortran back in
the day - so DEC marketing thought in those terms.

I remember that CMU's Mellon Institute built an automated realtime
newspaper sorting/delivery system for the Pittsburgh Press and a number of
other newspapers and ended up using FORTRAN - because that's all they had
for RT11 that they trusted (thankfully that project started after I had
left, although I helped with the bidding and assessment). We had wanted to
use BLISS but that meant cross compiling from the 10's and the customer
wanted the system self hosting as I recall. By the time the Mellon folks
completed the project, OMSI's Pascal compiler for RT11 was available, but
the water was under the bridge.



> but its character handling was awful.
>
​Yep - but as others have pointed out, with something like RATFOR it could
be made usable and that's what a lot of people I know did when they had
too.   As I said, the FPS folks wrote a parallelizing, Fortran for the
FPS-164 in Ratfor A compiler, to me, is the definition if a character based
application if I can name one.




>   I ended up writing almost all that stuff in assembler
> ​ ​
> (which fortunately the PDP-11 is wonderful for).
>
> ​You and many others ;-)

Clem​
ᐧ
ᐧ
ᐧ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180320/35237ea8/attachment.html>


  parent reply	other threads:[~2018-03-20 21:36 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
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 [this message]
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='CAC20D2NNxp-3Qpw1=_3+3ZT6pk-b_answ88-KLZCw7j3gf7WOw@mail.gmail.com' \
    --to=clemc@ccc.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).