From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] long lived programs
Date: Fri, 23 Mar 2018 17:07:27 -0400 [thread overview]
Message-ID: <CAC20D2NK4BmREezVEryo4c0EYVR5dwVfSgOkVwrukd1Ou=6LkQ@mail.gmail.com> (raw)
In-Reply-To: <e4bb1950ab54f6b5319e718be78bbfe7738c6c00@webmail.yaccman.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
On Fri, Mar 23, 2018 at 4:50 PM, Steve Johnson <scj at yaccman.com> wrote:
> Another issue to consider. I once talked with someone who was designing
> nuclear reactors. They had a similar requirement to archive their design
> simulations. But in this case, part of the requirement was to pass some
> standard simulation tests (in FORTRAN, of course). He was complaining that
> these programs had bugs and didn't give the right answer. So they ran the
> corrected programs to make sure the thing would not blow up, and then
> tweaked their parameters so it would pass the buggy program that was
> written into law...
>
> Steve
>
That's not Fortran's problem -- that is our legal system.
ᐧ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180323/4e169ddf/attachment.html>
next prev parent reply other threads:[~2018-03-23 21:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 2:53 [TUHS] long lived programs (was Re: RIP John Backus Doug McIlroy
2018-03-23 18:27 ` Bakul Shah
2018-03-23 20:50 ` [TUHS] long lived programs Steve Johnson
2018-03-23 21:07 ` Clem Cole [this message]
2018-03-23 15:51 Ron Natalie
2018-03-23 15:57 ` Clem Cole
2018-03-23 16:25 ` Lars Brinkhoff
2018-03-23 16:59 ` Lawrence Stewart
2018-03-23 17:31 ` Steve Nickolas
2018-03-23 16:32 ` Ron Natalie
2018-04-05 21:03 Norman Wilson
2018-04-05 21:23 ` Clem Cole
2018-04-05 21:38 ` Bakul Shah
2018-04-06 2:03 ` Random832
2018-04-06 4:27 ` Warner Losh
2018-04-06 4:31 ` Jon Steinhart
2018-04-06 4:58 ` Steve Nickolas
2018-04-06 5:02 ` Jon Steinhart
2018-04-06 4:29 ` Steve Johnson
2018-04-06 5:57 ` Bakul Shah
2018-04-06 21:52 ` Peter Jeremy
2018-04-05 22:46 ` Arthur Krewat
2018-04-05 23:23 ` Paul Winalski
2018-04-05 23:33 ` Arthur Krewat
2018-04-06 0:05 ` Toby Thain
2018-04-06 4:51 ` Dave Horsfall
2018-04-06 15:00 ` Tony Finch
2018-04-07 20:41 ` Paul Winalski
2018-04-06 22:33 Doug McIlroy
2018-04-07 1:01 ` Paul Winalski
2018-04-07 1:09 ` Larry McVoy
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='CAC20D2NK4BmREezVEryo4c0EYVR5dwVfSgOkVwrukd1Ou=6LkQ@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).