From 4403ad91d0ff0c63820f23d8a1bc4c489917ab30 Mon Sep 17 00:00:00 2001
From: jim
Date: Wed, 25 Feb 2015 10:50:20 -0500
Subject: [PATCH] wording
---
exercises/assignment4.mdwn | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/exercises/assignment4.mdwn b/exercises/assignment4.mdwn
index fbda153a..3786a61b 100644
--- a/exercises/assignment4.mdwn
+++ b/exercises/assignment4.mdwn
@@ -109,7 +109,7 @@ For instance, `fact 0 ~~> 1`, `fact 1 ~~> 1`, `fact 2 ~~> 2`, `fact 3 ~~>
Some limitations of this scheme: there is no easy way to label an inner, branching node (for example with a syntactic category like VP), and there is no way to represent a tree in which a mother node has a single daughter.
- When processing a tree, you can test for whether the tree is a leaf node (that is, contains only a single number), by testing whether the length of the list is 1. This will be your base case for your recursive definitions that work on these trees. (You'll probably want to write a function `leaf?` that compartmentalizes this check.)
+ When processing a tree, you can test for whether the tree is a leaf node (that is, contains only a single number), by testing whether the length of the list is 1. This will be your base case for your recursive definitions that work on these trees. (You'll probably want to write a function `leaf?` that encapsulates this check.)
Your assignment is to write a Lambda Calculus function that expects a tree, encoded in the way just described, as an argument, and returns the sum of its leaves as a result. So for all of the trees listed above, it should return `1 + 2 + 3`, namely `6`. You can use any Lambda Calculus implementation of lists you like.
--
2.11.0