[Note workarounds for bugs.
malcolm**20041012095004] {
hunk ./docs/bugs.html 24
+    (See <a href="faq.html">FAQ</a> for workaround.)
hunk ./docs/bugs.html 26
-<li><em>hat-trans</em> output can fail at link time if the arity
-   of source definitions or applications is large.
+<li><em>hat-trans</em> can fail if the arity of source definitions
+    or applications is large.
+    (See <a href="faq.html">FAQ</a> for workaround.)
hunk ./docs/bugs.html 122
-This page last modified: 13th March 2003<br>
+This page last modified: 27th July 2004<br>
hunk ./docs/faq.html 56
+<h3>I don't seem to be able to build Hat-2.02 with ghc-6.x</h3>
+
+<p>
+The hat-2.02 package is quite old now and does not build cleanly
+with ghc &ge; 6.0.  All the problems are already fixed in CVS, and we
+do hope to release an updated package in the near to mid future,
+but in the meantime, we recommend that ghc-6.x users use our
+<a href="cvs.html">anonymous CVS repository</a> to get a working
+version of Hat.
+
hunk ./docs/faq.html 69
-Hat covers the complete Haskell 98 language and its libraries, or
+Hat covers the complete Haskell'98 language and its libraries, or
hunk ./docs/faq.html 77
+<h3>Compiling for tracing gives me an error like: Ambiguous type
+variable `a' in top-level constraint `Num a'</h3>
+
+<p>
+You have been hit by Haskell's defaulting rules for numeric literals,
+which unfortunately means you need to add one or more type signatures
+to your code.  In the rejected module, add the line "default ()",
+and recompile it normally (not for tracing).  You will now see an
+error of similar form to the error you saw when compiling for tracing,
+except that the line number refers to your original code.  Fix this
+error by adding a type signature, e.g. (0::Int) instead of just 0.
+Now if your original code compiles cleanly again, it will also compile
+properly for tracing.
+
+<h3>hat-trans fails with an error like: Cannot handle field update with
+more than 2 labels; attempted arity 11</h3>
+
+<p>
+Hat has some numeric limits on the size of certain constructs it
+can handle.  Usually, there is a simple syntactic change you can make
+to your original source code to get round the limitation.  For instance:
+<ul>
+<li> <em>Field updates.</em> You can re-write a large field update
+  to become a chain of smaller field updates, each with no more than
+  two labels.  e.g. change <pre>x { a=1, b=2, c=3, d=4, e=5 }</pre>
+  to <pre>x { a=1, b=2 } { c=3, d=4 } { e=5 }</pre>
+
+<li> <em>Large applications.</em> You can re-write a large function or
+  constructor application using parentheses to become a chain of smaller
+  nested applications, each with no more than the stated arity.  e.g. change
+  <pre>f a b c d e g h i j k</pre> to <pre>(((f a b c d) e g h i) j k</pre>
+</ul>
+
hunk ./docs/faq.html 120
-This page last modified: 5th February 2003<br>
+This page last modified: 27th July 2004<br>
}