Hi Ladislav, LM> My reasons are more technical, though...We want SET to be able to LM> accept a result of an expression... LM> If we used the nontransparent argument passing, this wouldn't be LM> possible, because the first argument wouldn't be evaluated.
Yes, I remembered the reasoning, sorry I didn't include it in my message; I should have. LM> In the case of the COLLECT function we can pick the nontransparent LM> argument passing, because it is improbable we would want to use a result LM> of an expression as the EMIT argument. I agree. LM> But I (personally) don't think it is a good practice to use LM> nontransparent argument passing anywhere and don't see any LM> advantages of doing it. (nice flame bait, isn't it?) Excellent flame bait! :) I think the perceived advantage may have been usability, in not having to remember to use a lit-word! value. Of course, SET and GET require it, as do a few others. How much code do we want to break, and what is the practical advantage? This would be a *really* good topic for Carl to address. Maybe post it in the Ask the Guru section of REBOLTalk? -- Gregg -- To unsubscribe from the list, just send an email to lists at rebol.com with unsubscribe as the subject.
