diff options
| -rw-r--r-- | 011load.cc | 3 | ||||
| -rw-r--r-- | 012transform.cc | 3 | ||||
| -rw-r--r-- | 020run.cc | 3 |
3 files changed, 9 insertions, 0 deletions
diff --git a/011load.cc b/011load.cc index b887c369..ab0d44bf 100644 --- a/011load.cc +++ b/011load.cc @@ -1,4 +1,7 @@ //: Phase 1 of running mu code: load it from a textual representation. +//: +//: The process of running mu code: +//: load -> transform -> run :(scenarios load) // use 'load' instead of 'run' in all scenarios in this layer :(scenario first_recipe) diff --git a/012transform.cc b/012transform.cc index b5b6e4fe..7ed7c0f8 100644 --- a/012transform.cc +++ b/012transform.cc @@ -1,5 +1,8 @@ //: Phase 2: Filter loaded recipes through an extensible list of 'transforms'. //: +//: The process of running mu code: +//: load -> transform -> run +//: //: The hope is that this framework of transform tools will provide a //: deconstructed alternative to conventional compilers. //: diff --git a/020run.cc b/020run.cc index a2248c30..7ece0dd2 100644 --- a/020run.cc +++ b/020run.cc @@ -1,5 +1,8 @@ //: Phase 3: Start running a loaded and transformed recipe. //: +//: The process of running mu code: +//: load -> transform -> run +//: //: So far we've seen recipes as lists of instructions, and instructions point //: at other recipes. To kick things off mu needs to know how to run certain //: 'primitive' recipes. That will then give the ability to run recipes |