From: Nemo Nusquam <cym224@gmail.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] History of m6?
Date: Mon, 11 Nov 2019 19:07:21 -0500 [thread overview]
Message-ID: <f3eff4d6-1b19-e115-fa43-473812050d5f@gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.1911120954561.11612@aneurin.horsfall.org>
On 11/11/19 17:58, Dave Horsfall wrote:
> On Mon, 11 Nov 2019, Theodore Y. Ts'o wrote:
>
>> On Mon, Nov 11, 2019 at 11:10:26PM +0200, Arnold Robbins wrote:
>>> I guess I'll also ask, how widespread was the use of macro processors
>>> in high level languages? They were big for assembler, and PL/1 had
>>> a macro language, but I don't know of any other contemporary languages
>>> that had them. Were the general purpose macro processors used a lot?
>>> E.g. with Fortran or Cobol or ...
>
> Late trivia: it's PL/I, not PL/1; rumour has it that IBM trademarked
> them all up to PL/C i.e. PL/100...
Found nothing on TESS. Maybe copyright but I am not familiar with
copyright.
>
>> Well, there's Ratfor (Rational Fortran), which was implemented as a
>> preprocessor in front of Fortran. I don't think it was used a lot,
>> though....
>
> I think I used it once, on the principle that I'll try anything once;
> ugh...
I worked for a company that wrote everything on ratfor. #6-)
>
> -- Dave
next prev parent reply other threads:[~2019-11-12 0:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 21:10 Arnold Robbins
2019-11-11 22:18 ` Dennis Boone
2019-11-12 16:01 ` Leah Neukirchen
2019-11-11 22:31 ` Theodore Y. Ts'o
2019-11-11 22:58 ` Dave Horsfall
2019-11-12 0:07 ` Nemo Nusquam [this message]
2019-11-12 0:39 ` Dave Horsfall
2019-11-12 0:30 ` Clem cole
2019-11-16 16:27 ` SPC
2019-11-17 5:30 ` Dave Horsfall
2019-11-17 5:50 ` Larry McVoy
2019-11-17 18:12 ` Bakul Shah
2019-11-17 18:23 ` Michael Kjörling
2019-11-17 18:56 ` Bakul Shah
2019-11-17 22:46 ` Barry Stanly
2019-11-12 0:42 ` Dennis Boone
2019-11-11 22:37 ` Michael Kjörling
2019-11-12 1:09 ` Steve Johnson
2019-11-12 15:07 ` Clem Cole
2019-11-13 9:16 ` Thomas Paulsen
2019-11-13 12:20 ` Lars Brinkhoff
2019-11-13 12:50 ` Mike Markowski
2019-11-13 13:02 ` Lars Brinkhoff
2019-11-13 16:56 ` Paul Winalski
2019-11-13 19:19 ` Lars Brinkhoff
2019-11-13 19:21 ` Jon Steinhart
2019-11-14 9:26 ` Thomas Paulsen
2019-11-14 10:53 ` Lars Brinkhoff
2019-11-13 21:26 ` Dave Horsfall
2019-11-13 22:53 ` Jaap Akkerhuis
2019-11-12 15:15 Doug McIlroy
2019-11-13 7:38 ` arnold
2019-11-13 10:55 ` David Arnold
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=f3eff4d6-1b19-e115-fa43-473812050d5f@gmail.com \
--to=cym224@gmail.com \
--cc=tuhs@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).