From 4814bf94e75ffdcbd2a4093eb1ab67851980a37a Mon Sep 17 00:00:00 2001 From: "Kartik K. Agaram" Date: Thu, 1 Oct 2015 13:13:10 -0700 Subject: 2226 - standardize warning format Always show recipe name where error occurred. But don't show internal 'interactive' name for sandboxes, that's just confusing. What started out as warnings are now ossifying into errors that halt all execution. Is this how things went with C and Unix as well? --- 045space_surround.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to '045space_surround.cc') diff --git a/045space_surround.cc b/045space_surround.cc index 68d23c93..94a717a0 100644 --- a/045space_surround.cc +++ b/045space_surround.cc @@ -42,7 +42,7 @@ long long int space_index(const reagent& x) { for (long long int i = /*skip name:type*/1; i < SIZE(x.properties); ++i) { if (x.properties.at(i).first == "space") { if (SIZE(x.properties.at(i).second) != 1) - raise << current_recipe_name() << ": /space metadata should take exactly one value in " << x.original_string << '\n' << end(); + raise << maybe(current_recipe_name()) << "/space metadata should take exactly one value in " << x.original_string << '\n' << end(); return to_integer(x.properties.at(i).second.at(0)); } } -- cgit 1.4.1-2-gfad0