diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2016-07-21 19:22:03 -0700 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2016-07-21 19:22:03 -0700 |
| commit | 8d72e5652147a0218f36757fd9171f3f2beda887 (patch) | |
| tree | b95edd6bb86f7d421327d2f436e0c2d375cb795d /091run_interactive.cc | |
| parent | fc19980d91e306df87b308d0c2875a2dcaf4b5c7 (diff) | |
| download | mu-8d72e5652147a0218f36757fd9171f3f2beda887.tar.gz | |
3120
Always show instruction before any transforms in error messages. This is likely going to make some errors unclear because they *need* to show the original instruction. But if we don't have tests for those situations did they ever really work?
Diffstat (limited to '091run_interactive.cc')
| -rw-r--r-- | 091run_interactive.cc | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/091run_interactive.cc b/091run_interactive.cc index 70dbed0f..b88333bd 100644 --- a/091run_interactive.cc +++ b/091run_interactive.cc @@ -30,7 +30,7 @@ put(Recipe_ordinal, "run-interactive", RUN_INTERACTIVE); :(before "End Primitive Recipe Checks") case RUN_INTERACTIVE: { if (SIZE(inst.ingredients) != 1) { - raise << maybe(get(Recipe, r).name) << "'run-interactive' requires exactly one ingredient, but got '" << to_original_string(inst) << "'\n" << end(); + raise << maybe(get(Recipe, r).name) << "'run-interactive' requires exactly one ingredient, but got '" << inst.original_string << "'\n" << end(); break; } if (!is_mu_string(inst.ingredients.at(0))) { @@ -436,7 +436,7 @@ put(Recipe_ordinal, "reload", RELOAD); :(before "End Primitive Recipe Checks") case RELOAD: { if (SIZE(inst.ingredients) != 1) { - raise << maybe(get(Recipe, r).name) << "'reload' requires exactly one ingredient, but got '" << to_original_string(inst) << "'\n" << end(); + raise << maybe(get(Recipe, r).name) << "'reload' requires exactly one ingredient, but got '" << inst.original_string << "'\n" << end(); break; } if (!is_mu_string(inst.ingredients.at(0))) { |