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 /012transform.cc | |
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 '012transform.cc')
-rw-r--r-- | 012transform.cc | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/012transform.cc b/012transform.cc index f3c76e38..614e53ed 100644 --- a/012transform.cc +++ b/012transform.cc @@ -15,7 +15,6 @@ vector<transform_fn> Transform; :(code) void transform_all() { -//? cerr << "AAA transform_all\n"; //? 2 for (long long int t = 0; t < SIZE(Transform); ++t) { for (map<recipe_ordinal, recipe>::iterator p = Recipe.begin(); p != Recipe.end(); ++p) { recipe& r = p->second; @@ -29,7 +28,6 @@ void transform_all() { } void parse_int_reagents() { -//? cout << "parse_int_reagents\n"; //? 1 for (map<recipe_ordinal, recipe>::iterator p = Recipe.begin(); p != Recipe.end(); ++p) { recipe& r = p->second; if (r.steps.empty()) continue; |