From: "David Baelde" <david.baelde@gmail.com>
To: Ocaml <caml-list@inria.fr>
Subject: Implementation of a prover
Date: Mon, 12 Mar 2007 22:41:27 +0100 [thread overview]
Message-ID: <53c655920703121441k5004991et194b046ebb601a8a@mail.gmail.com> (raw)
Hi list,
There are well-known implementation techniques for depth-first theorem
proving, using continuation-passing style (success/failure
continuations). But these techniques do not easily allow the building
of a proof witness. This is nice when you have a working proof-search
procedure but not when you're still playing with a logic, trying to
find the right procedure or more generally when you just want an
interactive prover.
I've started to look for a way to define rules as tactics in such a
way that these core functions can be used with or without a proof
witness construction procedure. I've had enough for today and I wanted
to know if anyone done that or knows a link to anything like that.
Any idea?
--
David
next reply other threads:[~2007-03-12 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 21:41 David Baelde [this message]
2007-04-11 23:55 ` [Caml-list] " Harrison, John R
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=53c655920703121441k5004991et194b046ebb601a8a@mail.gmail.com \
--to=david.baelde@gmail.com \
--cc=caml-list@inria.fr \
--cc=david.baelde@ens-lyon.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