On 11/27/07, Tammo van Lessen <[EMAIL PROTECTED]> wrote: > > > var = parterlink.me.op(corr => cset1) > > var = partnerlink.partner.op(setCorr => cset2, corr => cset1) > While seeing the ADA-style params again, the ambiguity problem could > also be solved by explicitly null-ing the inputVariable > > var = partnerLink.op(input => empty) //empty is a reserved keyword > > instead of "empty", "null" is also fine.
The thing I'm concerned about is ambiguity to the reader, not the process engine. In most cases the process engine will be able to resolve the ambiguity simply from not having the same operation available on both ports. But reading the process definition, plink.foo is confusing, I can't just by reading determing if it's invoking or receiving without also digging into the operation definition. And me/partner is just another way of saying receive/invoke, so why not say it directly? Assaf > Just a few thoughts... > > Best, > Tammo > -- CTO, Intalio http://www.intalio.com
