[Swift-devel] multiple arguments
Ben Clifford
benc at hawaga.org.uk
Wed May 2 10:37:30 CDT 2007
On Wed, 2 May 2007, Yong Zhao wrote:
> That's strange. I used @filenames a lot a while ago and never had any
> problems. Check the kml translation, maybe you added the getfieldvalue
> stuff to getFilenames, which should not happen. i.e.
yeah, I was just checking that out as a probable cause.
As of about r650, getField is used on all function invocations when a
variable/path name is supplied as a parameter, no matter which function
name is used.
The semantics of these 'multiple valued' language constructs ([*] and how
that passes through @filenames, for example) seems (still) quite poorly
defined...
>
> It needs to be
> <vdl:getFilenames var="{sliced}">
> <argument name="path"> ....</...>
> </...>
>
> not
> <vdl:getFilenames><vdl:getFieldvalue ....>
>
>
> Yong.
>
> On Wed, 2 May 2007, Ben Clifford wrote:
>
> >
> >
> > On Wed, 2 May 2007, Yong Zhao wrote:
> >
> > > use @filenames(sliced[*].img).
> >
> > I get this:
> >
> > Execution failed:
> > org.griphyn.vdl.mapping.InvalidPathException: Invalid path (*.img)
> > for type volume
> >
> >
> > I tried something a little simpler:
> >
> >
> > type file;
> >
> > (file out) echo(file n[])
> > {
> > app {
> > echo @filenames(n) stdout=out;
> > }
> > }
> >
> >
> > file f[] <fixed_array_mapper;files="a b c">;
> >
> > file out;
> >
> > out=echo(f);
> >
> >
> > but that hangs...
> >
> > oof.
> >
> > --
> >
>
>
More information about the Swift-devel
mailing list