1155 - three phases of mu: load, transform, run

Each phase implicitly calls previous phases.
Most C++ scenarios implicitly call one, two or three of the phases.
More clear now that 'load' does more than just add recipes.

1 files changed, 3 insertions, 6 deletions

diff --git a/cpp/040brace b/cpp/040brace
index 75dbf457..e79f6100 100644
--- a/cpp/040brace
+++ b/cpp/040brace
@@ -19,7 +19,7 @@
 //: benefits of the control-flow primitives we're used to in other languages,
 //: like 'if', 'while', 'for', etc.
 
-:(scenarios transform_test)
+:(scenarios transform)
 :(scenario "brace_conversion")
 recipe main [
   {
@@ -160,12 +160,9 @@ size_t matching_brace(size_t index, const list<pair<int, size_t> >& braces) {
 }
 
 // temporarily suppress run
-void transform_test(string form) {
-//?   cout << "AAA transform_test {\n"; //? 1
-  add_recipes(form);
-//?   cout << "AAA done adding recipes\n"; //? 1
+void transform(string form) {
+  load(form);
   transform_all();
-//?   cout << "AAA }\n"; //? 1
 }
 
 //: Make sure these pseudo recipes get consistent numbers in all tests, even