aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--README.md2
-rw-r--r--ch09/9_a_1.txt13
2 files changed, 14 insertions, 1 deletions
diff --git a/README.md b/README.md
index 14ce202..43d6d3c 100644
--- a/README.md
+++ b/README.md
@@ -124,7 +124,7 @@ are prefixed with 'Module_'.
| **_Module_8_c_1_** | yes | 211 | |
| 8_c_2 | yes | | |
| **_8_d_1_** | yes | 212 | |
-| **_9_a_1_** | | 221 | 9. I/O case study: a library for searching the filesystem |
+| **_9_a_1_** | yes | 221 | 9. I/O case study: a library for searching the filesystem |
| **_9_b_1_** | | 228 | |
| 9_b_2 | | | |
| 9_b_3 | | | |
diff --git a/ch09/9_a_1.txt b/ch09/9_a_1.txt
new file mode 100644
index 0000000..0fa7bb6
--- /dev/null
+++ b/ch09/9_a_1.txt
@@ -0,0 +1,13 @@
+-- Is the order in which we call bracket and handle important? Why?
+
+-- The assignment is not completely clear. The 'bracket' function has three
+-- actions. It's not clear what the order means here. When changing the order of
+-- the 'bracket' and 'handle', 'handle' can be used in just one action or in
+-- more of them.
+--
+-- Let's assume that changing the order means moving the 'handle' call to the
+-- "use" action of the 'bracket' so that it covers that whole action.
+
+-- The order is important. When the order is changed (see the assumption above),
+-- exceptions thrown in the "acquire" and "release" actions will not be caught
+-- by the 'handle' function.