about summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2015-05-20 19:51:29 -0700
committerKartik K. Agaram <vc@akkartik.com>2015-05-20 19:51:29 -0700
commitf22059b3bcbaf9c8736759df080cea1a87a9e1a6 (patch)
treebd61af185a40aeb839e694dbfc58dcd087a4e7df
parent0a6d127d3758a1f76ace9dfe7c83772d7089f4c0 (diff)
downloadmu-f22059b3bcbaf9c8736759df080cea1a87a9e1a6.tar.gz
1411
-rw-r--r--003trace.cc7
1 files changed, 5 insertions, 2 deletions
diff --git a/003trace.cc b/003trace.cc
index cdef3c0f..dfcc02a1 100644
--- a/003trace.cc
+++ b/003trace.cc
@@ -47,8 +47,11 @@
 //: right test to debug can be an important skill to pick up.
 //:
 //: A final wrinkle is for recursive functions; it's often useful to segment
-//: calls of different depth in the trace:
-//:   +eval/1: => 34  # the topmost call to eval should have logged this line
+//: calls of different depth in the trace. Assuming a recursive function emits
+//: this line:
+//:   foo: 34
+//: this checks that the *topmost* call to the function emits it:
+//:   +foo/1: 34
 //: (look at new_trace_frame below)
 //:
 //: To build robust tests, trace facts about your domain rather than details of