From: Tony Finch <dot@dotat.at>
To: "Perry E. Metzger" <perry@piermont.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Formal Specification and Verification (was Re: TUHS Digest, Vol 33, Issue 5)
Date: Mon, 20 Aug 2018 19:48:15 +0100 [thread overview]
Message-ID: <alpine.DEB.2.20.1808201939560.3596@grey.csi.cam.ac.uk> (raw)
In-Reply-To: <20180818155733.523a3d2d@jabberwock.cb.piermont.com>
Perry E. Metzger <perry@piermont.com> wrote:
>
> This is a pretty long posting. If you don't care to read it, the TL;DR
> is that formal specification and verification is now a real
> discipline, which it wasn't in the old days, and there are systems to
> do it in, and it's well understood.
Another example, of a somewhat different flavour, is
http://lamport.azurewebsites.net/tla/amazon.html
The difference being that I gather Amazon are using TLA+ more as a
modelling language for distributed systems and not strictly for verifying
implementations.
PS. If there is a historical Lamport / Unix connection, I'm not aware of
one...
Tony.
--
f.anthony.n.finch <dot@dotat.at> http://dotat.at/
protect and enlarge the conditions of liberty and social justice
prev parent reply other threads:[~2018-08-20 18:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 13:06 [TUHS] TUHS Digest, Vol 33, Issue 5 Noel Chiappa
2018-08-06 15:52 ` Bakul Shah
2018-08-06 16:30 ` Hellwig Geisse
2018-08-06 21:19 ` Steve Johnson
2018-08-18 19:57 ` [TUHS] Formal Specification and Verification (was Re: TUHS Digest, Vol 33, Issue 5) Perry E. Metzger
2018-08-19 23:47 ` George Michaelson
2018-08-20 0:57 ` Perry E. Metzger
2018-08-20 3:29 ` [TUHS] Formal Specification and Verification Warren Toomey
2018-08-20 18:48 ` Tony Finch [this message]
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=alpine.DEB.2.20.1808201939560.3596@grey.csi.cam.ac.uk \
--to=dot@dotat.at \
--cc=perry@piermont.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).