Mon Feb 4 06:29:28 PST 2002 olaf * Write traced reductions called from untraced code correctly to trace. Example: filter myEven [1..10]; myEven x = x filter is untraced, but because myEven is traced the reductions myEven 1 = False, myEven 2 = True, ... should be in the trace. The "fun?" combinators responsible for this wrote the application but not the following Sat pointing to the result into the trace. After changing that it works. However, hat-detect cannot find such kind of children and hat-trail does not seem to have any trace pointing to them either; the trail is rather weird. Note that if myEven is defined as "myEven = even", then hat-observe myEven will only return myEven = even which is correct but not terribly useful. M ./src/hatlib/Hat.hs -5 +12