[Swift-devel] remote file/directory stuff (bug 22)

[Yong Zhao]

Hi,

Can you elaborate on this issue a little bit so that we can make a
unanimous decision:

1. what was the problem exactly

2. what are you proposing

3. to what extent does the proposal solve the problem

4. what is the implication to the mapping interface

Thanks.
Yong.

On Tue, 27 Feb 2007, Mihael Hategan wrote:

> If you can make this translate into something like vdl:(in|
> out)appmapping(var, path, dest), preferably after the stagein/stageout
> directives, I can probably make it work.
>
> On Tue, 2007-02-27 at 19:22 +0000, Ben Clifford wrote:
> >
> > On Mon, 26 Feb 2007, Mihael Hategan wrote:
> >
> > > Right. This would be the "application mapper".
> > > Now, there are a few things here:
> > > We may also want to do the same to the input, because some even more
> > > twisted apps will not even accept that as a parameter. So:
> > > (file k, file m, file n) myapp(file l) {
> > >   app{
> > >     l>"input.txt";
> > >     myapp;
> > >     k<"output.crd"
> > >     m<"output.prd"
> > >     n<"output.rtf"
> > >   }
> > > }
> >
> > so something like the above syntax, sufficient to address Nika's cases, is
> > probably the way to go for bug 22, without necessarily implementing more
> > complicated stuff like arrays below.
> >
> > That should give us a feel for how the concept works in practice too.
> >
> > > This may become a little trickier when inputs (or even outputs) are
> > > arrays, so we may need nicer schemes:
> > > (file o) myapp(file i[]){
> > >   app{
> > >     i[x=*] > "input"+$1; (or something like that)
> > >     myapp;
> > >     ...
> > >   }
> > > }
> >
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>