author wenzelm
Sat, 05 Apr 2014 15:03:40 +0200
changeset 56421 1ffd7eaa778b
parent 54572 95a33ff3984b
permissions -rw-r--r--
updated to jedit_build-20140405: Code2HTML.jar, CommonControls.jar, Console.jar, kappalayout.jar, Navigator.jar, SideKick.jar, doc with jEdit manuals (ant dist-manuals);

Isabelle is a generic system for
implementing logical formalisms, and Isabelle/HOL is the specialization
of Isabelle for HOL, which abbreviates Higher-Order Logic. We introduce
HOL step by step following the equation
\[ \mbox{HOL} = \mbox{Functional Programming} + \mbox{Logic}. \]
We assume that the reader is used to logical and set theoretic notation
and is familiar with the basic concepts of functional programming.
Open-minded readers have been known to pick up functional
programming through the wealth of examples in \autoref{sec:FP}
and \autoref{sec:CaseStudyExp}.

\autoref{sec:FP} introduces HOL as a functional programming language and
explains how to write simple inductive proofs of mostly equational properties
of recursive functions.
\autoref{sec:CaseStudyExp} contains a
small case study: arithmetic and boolean expressions, their evaluation,
optimization and compilation.
\autoref{ch:Logic} introduces the rest of HOL: the
language of formulas beyond equality, automatic proof tools, single
step proofs, and inductive definitions, an essential specification construct.
\autoref{ch:Isar} introduces Isar, Isabelle's language for writing structured

%Further material (slides, demos etc) can be found online at

% Relics:
% We aim to minimise the amount of background knowledge of logic we expect
% from the reader
% We have focussed on the core material
% in the intersection of computation and logic.

This introduction to the core of Isabelle is intentionally concrete and
example-based: we concentrate on examples that illustrate the typical cases
without explaining the general case if it can be inferred from the examples.
We cover the essentials (from a functional programming point of view) as
quickly and compactly as possible.
After all, this book is primarily about semantics.

For a comprehensive treatment of all things Isabelle we recommend the
\emph{Isabelle/Isar Reference Manual}~\cite{IsarRef}, which comes with the
Isabelle distribution.
The tutorial by Nipkow, Paulson and Wenzel~\cite{LNCS2283} (in its updated version that comes with the Isabelle distribution) is still recommended for the wealth of examples and material, but its proof style is outdated. In particular it does not cover the structured proof language Isar.

%This introduction to Isabelle has grown out of many years of teaching
%Isabelle courses. 

\subsection*{Getting Started with Isabelle}

If you have not done so already, download and install Isabelle
from \url{}. You can start it by clicking
on the application icon. This will launch Isabelle's
user interface based on the text editor \concept{jedit}. Below you see
a typical example snapshot of a jedit session. At this point we merely explain
the layout of the window, not its contents.

The upper part of the window shows the input typed by the user, i.e.\ the
gradually growing Isabelle text of definitions, theorems, proofs, etc.  The
interface processes the user input automatically while it is typed, just like
modern Java IDEs.  Isabelle's response to the user input is shown in the
lower part of the window. You can examine the response to any input phrase
by clicking on that phrase or by hovering over underlined text.

This should suffice to get started with the jedit interface.
Now you need to learn what to type into it.
If you want to apply what you have learned about Isabelle we recommend you
donwload and read the book
Semantics}~\cite{ConcreteSemantics}, a guided tour of the wonderful world of
programming langage semantics formalised in Isabelle.  In fact,
\emph{Programming and Proving in Isabelle/HOL} constitutes part~I of
\href{}{Concrete Semantics}.  The web
pages for \href{}{Concrete Semantics}
also provide a set of \LaTeX-based slides for teaching \emph{Programming and
Proving in Isabelle/HOL}.

I wish to thank the following people for their comments on this document:
Florian Haftmann, Ren\'{e} Thiemann, Sean Seefried, Christian Sternagel
and Carl Witty.