[Swift-devel] Path.parse(path.toString())

[Michael Wilde]

So far Im not able to re-create this problem on the prior revision of 0.93.

Im currently using this variation of the script Mihael posted below:

type file;

type struct {
        file b;
        file c;
}

app (struct of) echo() {
  sh "-c" "echo bee >fileb ; echo see >filec";
}

struct s <ext;exec="structbug1.map">;

s = echo();

I discovered what I think is a new bug in the process: if the shell command string contains the characters >&1 and >&2, Swift complains that it cant process the intermediate xml. Presumably those shell sequences are getting xml parsing confused and need to be escaped.

- Mike

----- Original Message -----
> From: "Mihael Hategan" <hategan at mcs.anl.gov>
> To: "David Kelly" <davidk at ci.uchicago.edu>
> Cc: "Swift Devel" <swift-devel at ci.uchicago.edu>
> Sent: Friday, September 9, 2011 1:31:44 AM
> Subject: Re: [Swift-devel] Path.parse(path.toString())
> On Fri, 2011-09-09 at 01:10 -0500, David Kelly wrote:
> > It looks like there are a few scripts in the test suite which write
> > structs and seem to be passing.
> 
> I suspect they are not staging structs out (just in).
> 
> >  Do you happen to have an example script I could add to the suite?
> 
> type file;
> 
> type struct {
> file b;
> file c;
> }
> 
> app (struct of) echo() {
> bash "echo bee >1 ; echo see >2" stdout=@filename(of.b)
> stderr=@filename(of.c);
> }
> 
> struct s <simple_mapper;>;
> 
> s = echo();
> 
> (I'm not sure if this actually works if the bug is fixed, but I know
> it
> doesn't if it isn't. Anyway, you get the idea).
> 
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel

-- 
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory