doc-src/IsarImplementation/implementation.tex
author Walther Neuper <neuper@ist.tugraz.at>
Thu, 12 Aug 2010 15:03:34 +0200
branchisac-from-Isabelle2009-2
changeset 37913 20e3616b2d9c
parent 35031 2ddc7edce107
child 40261 0de42180febe
permissions -rw-r--r--
prepare reactivation of isac-update-Isa09-2
     1 \documentclass[12pt,a4paper,fleqn]{report}
     2 \usepackage{latexsym,graphicx}
     3 \usepackage[refpage]{nomencl}
     4 \usepackage{../iman,../extra,../isar,../proof}
     5 \usepackage[nohyphen,strings]{../underscore}
     6 \usepackage{../isabelle,../isabellesym}
     7 \usepackage{style}
     8 \usepackage{../pdfsetup}
     9 
    10 
    11 \hyphenation{Isabelle}
    12 \hyphenation{Isar}
    13 
    14 \isadroptag{theory}
    15 \title{\includegraphics[scale=0.5]{isabelle_isar}
    16   \\[4ex] The Isabelle/Isar Implementation}
    17 \author{\emph{Makarius Wenzel}  \\[3ex]
    18   With Contributions by
    19   Florian Haftmann
    20   and Larry Paulson
    21 }
    22 
    23 \makeindex
    24 
    25 
    26 \begin{document}
    27 
    28 \maketitle
    29 
    30 \begin{abstract}
    31   We describe the key concepts underlying the Isabelle/Isar
    32   implementation, including ML references for the most important
    33   functions.  The aim is to give some insight into the overall system
    34   architecture, and provide clues on implementing applications within
    35   this framework.
    36 \end{abstract}
    37 
    38 \vspace*{2.5cm}
    39 \begin{quote}
    40 
    41   {\small\em Isabelle was not designed; it evolved.  Not everyone
    42     likes this idea.  Specification experts rightly abhor
    43     trial-and-error programming.  They suggest that no one should
    44     write a program without first writing a complete formal
    45     specification. But university departments are not software houses.
    46     Programs like Isabelle are not products: when they have served
    47     their purpose, they are discarded.}
    48 
    49   Lawrence C. Paulson, ``Isabelle: The Next 700 Theorem Provers''
    50 
    51   \vspace*{1cm}
    52 
    53   {\small\em As I did 20 years ago, I still fervently believe that the
    54     only way to make software secure, reliable, and fast is to make it
    55     small.  Fight features.}
    56 
    57   Andrew S. Tanenbaum
    58 
    59   \vspace*{1cm}
    60 
    61   {\small\em One thing that UNIX does not need is more features. It is
    62     successful in part because it has a small number of good ideas
    63     that work well together. Merely adding features does not make it
    64     easier for users to do things --- it just makes the manual
    65     thicker. The right solution in the right place is always more
    66     effective than haphazard hacking.}
    67 
    68   Rob Pike and Brian W. Kernighan
    69 
    70 \end{quote}
    71 
    72 \thispagestyle{empty}\clearpage
    73 
    74 \pagenumbering{roman}
    75 \tableofcontents
    76 \listoffigures
    77 \clearfirst
    78 
    79 \input{Thy/document/Prelim.tex}
    80 \input{Thy/document/Logic.tex}
    81 \input{Thy/document/Tactic.tex}
    82 \input{Thy/document/Proof.tex}
    83 \input{Thy/document/Syntax.tex}
    84 \input{Thy/document/Isar.tex}
    85 \input{Thy/document/Local_Theory.tex}
    86 \input{Thy/document/Integration.tex}
    87 
    88 \appendix
    89 \input{Thy/document/ML.tex}
    90 
    91 \begingroup
    92 \tocentry{\bibname}
    93 \bibliographystyle{abbrv} \small\raggedright\frenchspacing
    94 \bibliography{../manual}
    95 \endgroup
    96 
    97 \tocentry{\indexname}
    98 \printindex
    99 
   100 \end{document}
   101 
   102 
   103 %%% Local Variables:
   104 %%% mode: latex
   105 %%% TeX-master: t
   106 %%% End: