<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><font class="Apple-style-span" face="Times">Only in a round-about way. Maybe that is ok, it is just less intuitive than say:</font></div><div><font class="Apple-style-span" face="Times"><br></font></div><div><font class="Apple-style-span" face="Times">seq {</font></div><div><font class="Apple-style-span" face="Times"> A();</font></div><div><font class="Apple-style-span" face="Times"> B();</font></div><div><font class="Apple-style-span" face="Times">}</font></div><div><br></div><div>(IMHO)</div><div><br></div><div>Ian.</div><br><div><div>On Mar 24, 2009, at 12:02 PM, Ben Clifford wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br>you can express sequencing. that's what extern lets you do.<br><br>On Tue, 24 Mar 2009, Ian Foster wrote:<br><br><blockquote type="cite">These discussions are very reminiscent of PCN, where we had many of the same<br></blockquote><blockquote type="cite">issues.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">A reason then for wanting sequencing was for output.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">We introduced a sequential operator, which had the advantage that people could<br></blockquote><blockquote type="cite">say more directly what they meant.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Mar 24, 2009, at 9:06 AM, Ben Clifford wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">On Tue, 24 Mar 2009, Zhao Zhang wrote:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Say, Job A is broadcasting common data shared for all jobs. And Job B only<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">needs to know that Job A is done, so he could read the common data.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">ok, so there is a data dependency.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">You can externals (like Mike has been using on the swift-user list) to<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">represent data dependencies like that.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">app (external commonData) A() {<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">...<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">}<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">app B(external commonData) {<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">...<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">}<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">external d = A();<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">B(d);<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">d represents your shared data set - by declaring it as 'external' you say<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">that Swift should do data dependency handling, but should not attempt to<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">manage the data itself.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">d is mapped to the data, but in your head, rather than in Swift.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">-- <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Swift-devel mailing list<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="mailto:Swift-devel@ci.uchicago.edu">Swift-devel@ci.uchicago.edu</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel">http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel</a><br></blockquote></blockquote><blockquote type="cite"><br></blockquote></div></blockquote></div><br></body></html>