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

[David Kelly]

I've tried reproducing this bug in a few different ways with 0.93RC2, but have not been able to. I'm wondering if it is one of those bugs that is dependent upon a certain configuration setting? I have added a variation of this script to the test suite (langauge-behavior/datatypes/056-struct-stage-out.swift).

Given the recent commits in the last week or so - the struct staging out issue and coaster fixes, I'm thinking we should set the release to October 1st. This would give us the time to do another full round of testing. It would also give us a chance to put the finishing touches on the website. 0.94 would then have the full time allotted for development and testing before a November 1st release.

David


----- Original Message -----
> From: "Michael Wilde" <wilde at mcs.anl.gov>
> To: "Mihael Hategan" <hategan at mcs.anl.gov>
> Cc: "Swift Devel" <swift-devel at ci.uchicago.edu>, "David Kelly" <davidk at ci.uchicago.edu>
> Sent: Friday, September 9, 2011 9:33:23 AM
> Subject: Re: [Swift-devel] Path.parse(path.toString())
> 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