X-Git-Url: http://lambda.jimpryor.net/git/gitweb.cgi?p=lambda.git;a=blobdiff_plain;f=translating_between_OCaml_Scheme_and_Haskell.mdwn;h=4a4287a1e776a13524b7db78d2ef9de43fb83b00;hp=40f518aa37432985c95e088b632730c8bd9cea00;hb=a7d3954c76604eea8d2c392c5eb2f9d11891460a;hpb=a9bcd94f06158cf67f3b7bb5f0abaf63050d23eb

diff --git a/translating_between_OCaml_Scheme_and_Haskell.mdwn b/translating_between_OCaml_Scheme_and_Haskell.mdwn
index 40f518aa..4a4287a1 100644
--- a/translating_between_OCaml_Scheme_and_Haskell.mdwn
+++ b/translating_between_OCaml_Scheme_and_Haskell.mdwn
@@ -199,6 +199,12 @@ We will however try to give some general advice about how to translate between O
 		type person = name * address;;
 		type 'a personal_data = PD of 'a;;
 
+*	When a type only has a single variant, as with PersonalData, Haskell programmers will often use the same name for both the type and the value constructor, like this:
+
+		data PersonalData a = PersonalData a
+
+	The interpreter can always tell from the context when you're using the type name and when you're using the value constructor.
+
 *	The type constructors discussed above took simple types as arguments. In Haskell, types are also allowed to take *type constructors* as arguments:
 
 		data BarType t = Bint (t Integer) | Bstring (t string)