[kepler-dev] Connected port list of a channel
Stephen Andrew Neuendorffer
neuendor at eecs.berkeley.edu
Mon Jul 26 10:06:21 PDT 2004
Yes, this is rather annoying... It's something that is missing in the
actor syntax.
The easiest workaround is to use getRemoteReceivers, and to get the container
of the receiver corresponding to the channel you want.
Steve
At 09:59 AM 7/26/2004, Efrat Jaeger wrote:
>Hi Edward,
>
>Thanks for your responses.
>
>While adding all the fixes,, I've been working on graph traversing of momls
>and realized that there is no connectedPortList method for a specific
>channel. Currently, I assume all the relations are added to the relationList
>by the channels connecting order, but it may sometimes be confusing,
>especially if a channel is connected to an explicit. Do you suppose this
>could be added as well?
>
>Thanks,
>
>Efrat
>
>_______________________________________________
>kepler-dev mailing list
>kepler-dev at ecoinformatics.org
>http://www.ecoinformatics.org/mailman/listinfo/kepler-dev
More information about the Kepler-dev
mailing list