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 /056shape_shifting_recipe.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 '056shape_shifting_recipe.cc')
| -rw-r--r-- | 056shape_shifting_recipe.cc | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/056shape_shifting_recipe.cc b/056shape_shifting_recipe.cc index 5cbbfa59..a4485f6c 100644 --- a/056shape_shifting_recipe.cc +++ b/056shape_shifting_recipe.cc @@ -276,9 +276,9 @@ void compute_type_names(recipe& variant) { instruction& inst = variant.steps.at(i); trace(9993, "transform") << " instruction: " << to_string(inst) << end(); for (int in = 0; in < SIZE(inst.ingredients); ++in) - save_or_deduce_type_name(inst.ingredients.at(in), type_names, variant, " in '" + to_original_string(inst) + "'"); + save_or_deduce_type_name(inst.ingredients.at(in), type_names, variant, " in '" + inst.original_string + "'"); for (int out = 0; out < SIZE(inst.products); ++out) - save_or_deduce_type_name(inst.products.at(out), type_names, variant, " in '" + to_original_string(inst) + "'"); + save_or_deduce_type_name(inst.products.at(out), type_names, variant, " in '" + inst.original_string + "'"); } } |