[Swift-devel] could we set the job sequence without a file dependency?

[Ian Foster]

Only in a round-about way. Maybe that is ok, it is just less intuitive  
than say:

seq {
     A();
     B();
}

(IMHO)

Ian.

On Mar 24, 2009, at 12:02 PM, Ben Clifford wrote:

>
> you can express sequencing. that's what extern lets you do.
>
> On Tue, 24 Mar 2009, Ian Foster wrote:
>
>> These discussions are very reminiscent of PCN, where we had many of  
>> the same
>> issues.
>>
>> A reason then for wanting sequencing was for output.
>>
>> We introduced a sequential operator, which had the advantage that  
>> people could
>> say more directly what they meant.
>>
>>
>> On Mar 24, 2009, at 9:06 AM, Ben Clifford wrote:
>>
>>>
>>> On Tue, 24 Mar 2009, Zhao Zhang wrote:
>>>
>>>> Say, Job A is broadcasting common data shared for all jobs. And  
>>>> Job B only
>>>> needs to know that Job A is done, so he could read the common data.
>>>
>>> ok, so there is a data dependency.
>>>
>>> You can externals (like Mike has been using on the swift-user  
>>> list) to
>>> represent data dependencies like that.
>>>
>>> app (external commonData) A() {
>>> ...
>>> }
>>>
>>> app B(external commonData) {
>>> ...
>>> }
>>>
>>> external d = A();
>>> B(d);
>>>
>>> d represents your shared data set - by declaring it as 'external'  
>>> you say
>>> that Swift should do data dependency handling, but should not  
>>> attempt to
>>> manage the data itself.
>>>
>>> d is mapped to the data, but in your head, rather than in Swift.
>>>
>>> -- 
>>> _______________________________________________
>>> Swift-devel mailing list
>>> Swift-devel at ci.uchicago.edu
>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-devel/attachments/20090324/3485fa3a/attachment.html>