diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2015-08-28 23:21:48 -0700 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2015-08-28 23:25:21 -0700 |
| commit | 6c1376f8307a3c7b98dfd5ef09670bd15c05f399 (patch) | |
| tree | 7baa415602234e3619a710f4c23907666ef4b716 /065duplex_list.mu | |
| parent | c769b878f65247fff2f4dabaf7948709ff1dcadb (diff) | |
| download | mu-6c1376f8307a3c7b98dfd5ef09670bd15c05f399.tar.gz | |
2095
Finally terminate the experiment of keeping debug prints around. I'm also going to give up on maintaining counts. What we really need is two kinds of tracing: a) For tests, just the domain-specific facts, organized by labels. b) For debugging, just transient dumps to stdout. b) only works if stdout is clean by default. Hmm, I think this means 'stash' should be the transient kind of trace.
Diffstat (limited to '065duplex_list.mu')
| -rw-r--r-- | 065duplex_list.mu | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/065duplex_list.mu b/065duplex_list.mu index 65cb9592..0b0a47c5 100644 --- a/065duplex_list.mu +++ b/065duplex_list.mu @@ -73,7 +73,6 @@ scenario duplex-list-handling [ 4:address:duplex-list <- prev-duplex 4:address:duplex-list 13:number <- first-duplex 4:address:duplex-list 14:boolean <- equal 3:address:duplex-list, 4:address:duplex-list -#? $dump-trace #? 1 ] memory-should-contain [ 0 <- 0 # no modifications to null pointers |