From: Tom Manos <email@example.com>
Subject: Re: [TUHS] efl(1) anyone?
Date: Thu, 16 Dec 2021 12:56:49 -0500 [thread overview]
Message-ID: <CAOs6KDfBBuu8dE3-su2LT4+V85g9=+W6y1HgERYeQq4XHgqsLQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]
I'm late to the party here. Although I'm a gray hair, I didn't start using
UNIX until the early '80s, and though I've seen, and been curious about
efl, I've never used it. Fortran 4 was my first high-level language in
college in the '70s.
That said, I do remember efl being on an early PC based UNIX - Microport
SVR2. On later Microport UNIXen it was gone, but I can't remember whether
it disappeared on SVR3 or 4.
I currently play with 4.3BSD Quasijarus system on simh, which has efl. What
a fun system to play with! Maybe I'll give efl a try if I can find enough
docs to grok it.
On Wed, Dec 15, 2021 at 3:49 AM <firstname.lastname@example.org> wrote:
> Hi TUHS folks!
> After having reincarnated ratfor, I am wondering about Stuart Feldman's
> efl (extended fortran language). It was a real compiler that let you
> define structs, and generated more or less readable Fortran code.
> I have the impression that it was pretty cool, but that it just didn't
> catch on. So:
> - Did anyone here ever use it personally?
> - Is my impression that it didn't catch on correct? Or am I ignorant?
> Thoughts etc. welcome. :-)
[-- Attachment #2: Type: text/html, Size: 2112 bytes --]
next prev parent reply other threads:[~2021-12-16 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 8:44 arnold
2021-12-15 16:25 ` John Cowan
2021-12-16 17:56 ` Tom Manos [this message]
2021-12-16 22:38 ` Clem Cole
2021-12-16 23:41 ` Tom Manos
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).