[Pkg-haskell-commits] darcs: policy: Always put variables in <tt></tt> for consistency

[Ian Lynagh]

Thu Jul 29 20:05:57 UTC 2004  Ian Lynagh <igloo at earth.li>
  * Always put variables in <tt></tt> for consistency

    M ./haskell-policy.sgml -13 +13

Thu Jul 29 20:05:57 UTC 2004  Ian Lynagh <igloo at earth.li>
  * Always put variables in <tt></tt> for consistency
diff -rN -u old-policy/haskell-policy.sgml new-policy/haskell-policy.sgml
--- old-policy/haskell-policy.sgml	2010-11-05 15:02:33.397114706 +0000
+++ new-policy/haskell-policy.sgml	2010-11-05 15:02:33.409115340 +0000
@@ -143,9 +143,9 @@
                 </item>
                 <item>
                     If given an argument <tt>-o</tt> followed by another
-                    argument <var>x</var> will create the output
+                    argument <tt><var>x</var></tt> will create the output
                     program, or object file if <tt>-c</tt> has also been
-                    given, to the filename <var>x</var>.
+                    given, to the filename <tt><var>x</var></tt>.
                 </item>
                 <item>
                     The arguments <tt>-O0</tt>, <tt>-O1</tt>,
@@ -218,18 +218,18 @@
             Cabal package names match the regex
             <tt>[a-zA-Z][-a-zA-Z0-9]*</tt>, and the tools that
             manipulate them are case preserving only.
-            For your package, calculate the <var>cname</var> from the
+            For your package, calculate the <tt><var>cname</var></tt> from the
             Cabal package name by converting all uppercase letters to
             lowercase. If it is desirable for multiple versions of the
             same cabal package to be installed at once on a Debian
             system then you may append <tt>-<var>cversion</var></tt>,
-            where <var>cversion</var> is the cabal version.
+            where <tt><var>cversion</var></tt> is the cabal version.
         </p>
 
         <p>
             The Debian source package &should; be called
             <tt>lib<var>cname</var></tt> and, for each implementation
-            <var>impl</var> that it is built for, it &should; make a
+            <tt><var>impl</var></tt> that it is built for, it &should; make a
             <tt>lib<var>impl</var>-<var>cname</var>-dev</tt> binary
             package.
         </p>
@@ -244,14 +244,14 @@
 
         <p>
             Some Haskell compilers, such as GHC, perform cross-module
-            optimisations, such as inlining.
-            This means that even small
-            internal changes to a library <var>foo</var> can cause
-            programs that link with a library <var>bar</var> which links
-            uses <var>foo</var> to fail to link, or even to link
-            successfully but give incorrect results.
-            Therefore libraries &must; depend on the exact version of
-            other Haskell libraries that they were compiled against.
+            optimisations, such as inlining.  This means that even small
+            internal changes to a library <tt><var>foo</var></tt> can
+            cause programs that link with a library
+            <tt><var>bar</var></tt> which links uses
+            <tt><var>foo</var></tt> to fail to link, or even to link
+            successfully but give incorrect results.  Therefore
+            libraries &must; depend on the exact version of other
+            Haskell libraries that they were compiled against.
             Furthermore, they must build-depend on the exact version of
             the Haskell libraries they use in order to keep the packages
             in sync across all arches.