From: arnold@skeeve.com
To: tuhs@minnie.tuhs.org, steve@quintile.net
Subject: Re: [TUHS] efl
Date: Sun, 19 Dec 2021 00:54:10 -0700 [thread overview]
Message-ID: <202112190754.1BJ7sAMt028858@freefriends.org> (raw)
In-Reply-To: <2788C381-789B-4B66-8749-AB330D3D08C1@quintile.net>
Steve,
Were you not aware of struct(1)? It was in V7 and BSD. It would read
regular Fortran and turn it into ratfor.
I never used it, but I thought it was the coolest kind of thing.
Arnold
Steve Simon <steve@quintile.net> wrote:
> hi,
>
> having supported Pafec and then in a different job flow3d, i was most
> interested in anything that could make large fortran packages more
> manageable.
>
> there was a commercial package called Spag i which claimed to
> un-spagatti-ify your code which i always wanted but, could never afford.
>
> the best i managed was sed and awk scripts to split huge fortran files
> into one file per function and build a makefile. this at least made
> rebuilds quicker.
>
> i do not miss maintaining fortran code hacked by dozens of people over
> many decades.
>
> -Steve
>
next prev parent reply other threads:[~2021-12-19 7:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 8:11 Steve Simon
2021-12-19 7:54 ` arnold [this message]
2021-12-19 8:08 ` Bakul Shah
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=202112190754.1BJ7sAMt028858@freefriends.org \
--to=arnold@skeeve.com \
--cc=steve@quintile.net \
--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).