X-Git-Url: http://lambda.jimpryor.net/git/gitweb.cgi?p=lambda.git;a=blobdiff_plain;f=from_list_zippers_to_continuations.mdwn;h=da184c51dc6659fe369375d5685bbccabaf2f998;hp=07c348635117775683ff1af9461174e351dcf7b4;hb=c4a2655a636328b4e3fe183717402a02f1d97a90;hpb=b73d55e2b19231870478f491d3f7a051a765c116

diff --git a/from_list_zippers_to_continuations.mdwn b/from_list_zippers_to_continuations.mdwn
index 07c34863..da184c51 100644
--- a/from_list_zippers_to_continuations.mdwn
+++ b/from_list_zippers_to_continuations.mdwn
@@ -144,7 +144,7 @@ This means that we can now represent the unzipped part of our
 zipper---the part we've already unzipped---as a continuation: a function
 describing how to finish building a list.  We'll write a new
 function, `tc` (for task with continuations), that will take an input
-list (not a zipper!) and a continuation and return a processed list.
+list (not a zipper!) and a continuation `k` (it's conventional to use `k` for continuation variables) and return a processed list.
 The structure and the behavior will follow that of `tz` above, with
 some small but interesting differences.  We've included the orginal
 `tz` to facilitate detailed comparison:
@@ -155,11 +155,11 @@ some small but interesting differences.  We've included the orginal
 	    | (unzipped, 'S'::zipped) -> tz ((List.append unzipped unzipped), zipped)
 	    | (unzipped, target::zipped) -> tz (target::unzipped, zipped);; (* Pull zipper *)
 	
-	let rec tc (l: char list) (c: (char list) -> (char list)) =
+	let rec tc (l: char list) (k: (char list) -> (char list)) =
 	    match l with
-	    | [] -> List.rev (c [])
-	    | 'S'::zipped -> tc zipped (fun tail -> c (c tail))
-	    | target::zipped -> tc zipped (fun tail -> target::(c tail));;
+	    | [] -> List.rev (k [])
+	    | 'S'::zipped -> tc zipped (fun tail -> k (k tail))
+	    | target::zipped -> tc zipped (fun tail -> target::(k tail));;
 	
 	# tc ['a'; 'b'; 'S'; 'd'] (fun tail -> tail);;
 	- : char list = ['a'; 'b'; 'a'; 'b']
@@ -178,19 +178,19 @@ not be instantiated).
 
 I have not called the functional argument `unzipped`, although that is
 what the parallel would suggest.  The reason is that `unzipped` is a
-list, but `c` is a function.  That's the most crucial difference, the
+list, but `k` is a function.  That's the most crucial difference, the
 point of the excercise, and it should be emphasized.  For instance,
 you can see this difference in the fact that in `tz`, we have to glue
 together the two instances of `unzipped` with an explicit (and
 relatively inefficient) `List.append`.
-In the `tc` version of the task, we simply compose `c` with itself:
-`c o c = fun tail -> c (c tail)`.
+In the `tc` version of the task, we simply compose `k` with itself:
+`k o k = fun tail -> k (k tail)`.
 
 A call `tc ['a'; 'b'; 'S'; 'd']` yields a partially-applied function; it still waits for another argument, a continuation of type `char list -> char list`. We have to give it an "initial continuation" to get started. Here we supply *the identity function* as the initial continuation. Why did we choose that? Well, if
 you have already constructed the initial list `"abSd"`, what's the desired continuation? What's the next step in the recipe to produce the desired result, i.e, the very same list, `"abSd"`?  Clearly, the identity function.
 
 A good way to test your understanding is to figure out what the
-continuation function `c` must be at the point in the computation when
+continuation function `k` must be at the point in the computation when
 `tc` is called with the first argument `"Sd"`.  Two choices: is it
 `fun tail -> 'a'::'b'::tail`, or it is `fun tail -> 'b'::'a'::tail`?  The way to see if
 you're right is to execute the following command and see what happens: