From 83fcebf3210b638d9f8248e0007e9f0c9804980a Mon Sep 17 00:00:00 2001 From: "Kartik K. Agaram" Date: Mon, 13 Jul 2015 20:53:41 -0700 Subject: 1778 --- html/036call_reply.cc.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'html/036call_reply.cc.html') diff --git a/html/036call_reply.cc.html b/html/036call_reply.cc.html index 2738d935..ab73fdb7 100644 --- a/html/036call_reply.cc.html +++ b/html/036call_reply.cc.html @@ -64,7 +64,7 @@ case REPLY: { // just in case 'main' returns a value, drop it for now if (Current_routine->calls.empty()) goto stop_running_current_routine; const instruction& caller_instruction = current_instruction(); - // make reply results available to caller + // make reply products available to caller copy(ingredients.begin(), ingredients.end(), inserter(products, products.begin())); // check that any reply ingredients with /same-as-ingredient connect up // the corresponding ingredient and product in the caller. @@ -105,7 +105,7 @@ recipe f [ //: In mu we'd like to assume that any instruction doesn't modify its //: ingredients unless they're also products. The /same-as-ingredient inside //: the recipe's 'reply' will help catch accidental misuse of such -//: 'ingredient-results' (sometimes called in-out parameters in other languages). +//: 'ingredient-products' (sometimes called in-out parameters in other languages). :(scenario reply_same_as_ingredient) % Hide_warnings = true; -- cgit 1.4.1-2-gfad0