From 90f308d7f7864e9d9626032bda228fae7b262436 Mon Sep 17 00:00:00 2001 From: Christiaan Baaij Date: Mon, 22 Feb 2010 09:49:54 +0100 Subject: [PATCH] Fix some macro uses --- "c\316\273ash.lhs" | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git "a/c\316\273ash.lhs" "b/c\316\273ash.lhs" index a83750b..67cd589 100644 --- "a/c\316\273ash.lhs" +++ "b/c\316\273ash.lhs" @@ -814,14 +814,14 @@ data IntPair = IntPair Int Int In \CLaSH, unconstrained polymorphism is completely supported. Any function defined can have any number of unconstrained type - parameters. The \CLaSH compiler will infer the type of every such + parameters. The \CLaSH\ compiler will infer the type of every such argument depending on how the function is applied. There is one exception to this: The top level function that is translated, can not have any polymorphic arguments (since it is never applied, so there is no way to find out the actual types for the type parameters). - \CLaSH does not support user-defined type classes, but does use some + \CLaSH\ does not support user-defined type classes, but does use some of the builtin ones for its builtin functions (like \hs{Num} and \hs{Eq}). @@ -932,7 +932,7 @@ data IntPair = IntPair Int Int \end{code} Finally, higher order arguments are not limited to just builtin - functions, but any function defined in \CLaSH can have function + functions, but any function defined in \CLaSH\ can have function arguments. This allows the hardware designer to use a powerful abstraction mechanism in his designs and have an optimal amount of code reuse. -- 2.30.2