Changes between Version 11 and Version 12 of NewGhciDebugger

Timestamp:

04/08/07 09:52:33 (6 years ago)

Author:

guest

Comment:

--

NewGhciDebugger

@@ -12 +12 @@
 The general rule of thumb for breakpoints is that you can set a breakpoint on any thing which is not a value (though there are some exceptions). For example, a literal character is a value, but a case expression is not. 
 
-You '''can''' set breakpoints on the following syntactical things: (XXX) check this list carefully)
+We call the places where you can set breakpoints as '''breakable expressions''' (even if some of them aren't strictly expressions).
+
+You '''can''' set breakpoints on the following things: (XXX) Check this list carefully!
  1. Function applications. We allow breakpoints on partial applications, even though they are technically values. Also, if there is an application with more than one argument, we only allow breaks on the whole expression, not on the sub-applications within: e.g. for the expression `map f list`, we allow a break on the whole expression, but not on the sub-application of `map f`.
  2. Case expressions.
@@ -26 +28 @@
  3. Do blocks. XXX check this one
  4. List comprehensions. XXX check this one
-
-We call the places where you can set breakpoints as '''breakable expressions''' (even if some of them aren't strictly expressions).
 
 You can set a breakpoint in three ways: