# HG changeset patch # User wenzelm # Date 1403875496 -7200 # Node ID b441f330078b1d0fdc3a4b2c32eb134248b173e2 # Parent 9444489766a1822eee17d1edbd9456ccbfbf9866 minor renovation of slightly odd and old README; diff -r 9444489766a1 -r b441f330078b src/HOL/Library/README.html --- a/src/HOL/Library/README.html Fri Jun 27 11:30:42 2014 +0200 +++ b/src/HOL/Library/README.html Fri Jun 27 15:24:56 2014 +0200 @@ -23,12 +23,6 @@
-
Files - -
Avoid unnecessary scattering of theories over several files. Use -new-style theories only, as old ones tend to clutter the file space -with separate .thy and .ML files. -
Examples
Theories should be as ``generic'' as is sensible. Unused (or @@ -54,12 +48,6 @@ separate word constituents by underscores, as in foo_bar or Foo_Bar (this looks best in LaTeX output). -

- -Note that syntax is global; qualified names lose syntax on -output. Do not use ``exotic'' symbols for syntax (such as -\<oplus>), but leave these for user applications. -

Global context declarations
Only items introduced in the present theory should be declared @@ -67,42 +55,6 @@ rules from parent theories may result in strange behavior later, depending on the user's arrangement of import lists. -
Mathematical symbols - -
Non-ASCII symbols should be used as appropriate, with some -care. In particular, avoid unreadable arrows: ==> should -be preferred over \<Longrightarrow>. Use isabelle -unsymbolize to clean up the sources. - -

- -The following ASCII symbols of HOL should be generally avoided: -@, !, ?, ?!, %, better -use SOME, ALL (or \<forall>), -EX (or \<exists>), EX! (or -\<exists>!), \<lambda>, respectively. -Note that bracket notation [| |] looks bad in LaTeX -output. - -

- -Some additional mathematical symbols are quite suitable for both -readable sources and the output document: -\<Inter>, -\<Union>, -\<and>, -\<in>, -\<inter>, -\<le>, -\<not>, -\<noteq>, -\<notin>, -\<or>, -\<subset>, -\<subseteq>, -\<times>, -\<union>. -

Spacing
Isabelle is able to produce a high-quality LaTeX document from the @@ -111,10 +63,8 @@ text. Incidentally, output looks very good if common type-setting conventions are observed: put a single space after each punctuation character (",", ".", etc.), but none -before it; do not extra spaces inside of parentheses, unless the -delimiters are composed of multiple symbols (as in -[| |]); do not attempt to simulate table markup with -spaces, avoid ``hanging'' indentations. +before it; do not extra spaces inside of parentheses; do not attempt +to simulate table markup with spaces, avoid ``hanging'' indentations.