Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "Harrison, John R" <johnh@ichips.intel.com>
To: "David McClain" <David.McClain@Avisere.com>
Cc: "Harrison, John R" <johnh@ichips.intel.com>, <caml-list@inria.fr>
Subject: RE: [Caml-list] Formal Methods
Date: Thu, 30 Sep 2004 10:19:50 -0700	[thread overview]
Message-ID: <012676D607FCF54E986746512C22CE7D0FE7AC@orsmsx407> (raw)

[-- Attachment #1: Type: text/plain, Size: 2009 bytes --]

When he says that "theorem proving algorithms do not work [...] they
only prove trivial theorems",
he may just be out of date, or he may only be talking about completely
automatic provers. (Even
then his claim is a bit questionable: what about the Robbins Conjecture
etc.?)
 
I didn't notice anything about the relevance of the halting problem in
that page, so maybe it's
somewhere else. Anyway, it's clearly not relevant to proving the
correctness of typical real-world
algorithms, whatever he may or may not say.
 
His general dismissive attitude to formal methods is not uncommon. And
it's prefectly reasonable
to point out that modern computer systems can be so complex and
ill-defined that they are hardly
amenable to formal treatment. But a more balanced view would acknowledge
the significant
success of formal methods in certain niches, and their role in trying to
check that very unmastered
complexity. 
 
John.

	-----Original Message-----
	From: owner-caml-list@pauillac.inria.fr
[mailto:owner-caml-list@pauillac.inria.fr] On Behalf Of David McClain
	Sent: Thursday, September 30, 2004 8:51 AM
	To: caml-list@inria.fr
	Subject: [Caml-list] Formal Methods
	
	
	I have just been reviewing some papers by Greg Chaitin on
Algorithmic Complexity Theory, in which he boldly states that 

	"Similarly, proving correctness of software using formal methods
is hopeless. Debugging is done experimentally, by trial and error. And
cautious managers insist on running a new system in parallel with the
old one until they believe that the new system works." 

	from 

	http://www.cs.auckland.ac.nz/CDMTCS/chaitin/omega.html 

	He goes to great lengths to discuss the halting problem and its
implications for proving correctness of algorithms. 

	I wonder, as a non-specialist in this area, how the goals of FPL
squares with this result? 
	David McClain 
	Senior Corporate Scientist 
	Avisere, Inc. 

	david.mcclain@avisere.com 
	+1.520.390.7738 (USA) 



[-- Attachment #2: Type: text/html, Size: 4596 bytes --]

             reply	other threads:[~2004-09-30 17:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30 17:19 Harrison, John R [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-09-30 15:51 David McClain
2004-09-30 17:35 ` Jacques Carette
2004-09-30 18:42   ` Jon Harrop
2004-10-01  8:24   ` Thomas Fischbacher
2004-10-01  9:01     ` Achim Blumensath
2004-10-01  7:36 ` Jean-Christophe Filliatre
2004-10-01  7:51   ` Tom
2004-10-01  9:04   ` Martin Berger
2004-10-01  8:30 ` Hendrik Tews
2004-10-01  9:18   ` Martin Berger

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=012676D607FCF54E986746512C22CE7D0FE7AC@orsmsx407 \
    --to=johnh@ichips.intel.com \
    --cc=David.McClain@Avisere.com \
    --cc=caml-list@inria.fr \
    /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