diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2016-02-25 07:39:25 -0800 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2016-02-25 07:46:56 -0800 |
commit | f51e9f63b40ce3d5c4d40808bf1b7e83ab7d60ff (patch) | |
tree | 4730fc0e0e69e8537686730a7a233d84b54f0266 /045closure_name.cc | |
parent | b5ab709c53d3f8464e6358678a3c57a1fc6e64b8 (diff) | |
download | mu-f51e9f63b40ce3d5c4d40808bf1b7e83ab7d60ff.tar.gz |
2701 - turn some warnings into errors
I really have only one warning left: when somebody redefines a function. I think I'm going to just turn that into an error as well and drop the notion of warnings altogether. Anytime we find something wrong we stop running the program. This is a place where hygiene is justified.
Diffstat (limited to '045closure_name.cc')
-rw-r--r-- | 045closure_name.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/045closure_name.cc b/045closure_name.cc index cb258583..701c69fa 100644 --- a/045closure_name.cc +++ b/045closure_name.cc @@ -80,7 +80,7 @@ void collect_surrounding_spaces(const recipe_ordinal r) { trace(9993, "name") << "lexically surrounding space for recipe " << get(Recipe, r).name << " comes from " << surrounding_recipe_name << end(); //? cerr << "lexically surrounding space for recipe " << get(Recipe, r).name << " comes from " << surrounding_recipe_name << '\n'; if (!contains_key(Recipe_ordinal, surrounding_recipe_name)) { - raise << "can't find recipe providing surrounding space for " << get(Recipe, r).name << ": " << surrounding_recipe_name << '\n' << end(); + raise_error << "can't find recipe providing surrounding space for " << get(Recipe, r).name << ": " << surrounding_recipe_name << '\n' << end(); continue; } put(Surrounding_space, r, get(Recipe_ordinal, surrounding_recipe_name)); |