diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2015-04-17 11:22:59 -0700 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2015-04-17 11:22:59 -0700 |
commit | 2199940af170456929a3c4fe4d07d25afea6ae55 (patch) | |
tree | 178c2f4a4188c19da3bfd1a0b3f32ec6a82880e6 /cpp/010vm | |
parent | c18e17f22feaf308376f53f2f61775ddad0e4a9d (diff) | |
download | mu-2199940af170456929a3c4fe4d07d25afea6ae55.tar.gz |
1077
Diffstat (limited to 'cpp/010vm')
-rw-r--r-- | cpp/010vm | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/cpp/010vm b/cpp/010vm index db274622..de50bde0 100644 --- a/cpp/010vm +++ b/cpp/010vm @@ -132,10 +132,10 @@ enum primitive_recipes { MAX_PRIMITIVE_RECIPES, }; :(code) -// It's all very well to construct recipes out of other recipes, but we need -// to know how to do *something* out of the box. For the following -// recipes there are only codes, no entries in the book, because mu just knows -// what to do for them. +//: It's all very well to construct recipes out of other recipes, but we need +//: to know how to do *something* out of the box. For the following +//: recipes there are only codes, no entries in the book, because mu just knows +//: what to do for them. void setup_recipes() { Recipe.clear(); Recipe_number.clear(); Recipe_number["idle"] = IDLE; |