[Swift-devel] iterate behaviour round II

[Michael Wilde]

Right. So lets keep iterate semantically unchanged for now, then deprecate it when we have an approach thats clearly better. For 0.93 lets focus on making it work as currently described.

Lets consider deprecating it in some not-too-distant release and if possible remove it much later with sufficient notice to the user community.

- Mike

(Also note that where iterate is first mentioned in the user guide it has no until() clause.)


----- Original Message -----
> From: "Mihael Hategan" <hategan at mcs.anl.gov>
> To: "Michael Wilde" <wilde at mcs.anl.gov>
> Cc: "Swift Devel" <swift-devel at ci.uchicago.edu>
> Sent: Wednesday, August 3, 2011 12:24:12 PM
> Subject: Re: [Swift-devel] iterate behaviour round II
> On Wed, 2011-08-03 at 09:23 -0500, Michael Wilde wrote:
> > I propose that we do everything possible to ensure that the
> > semantics
> > of iterate does not change from 0.92.1, to avoid breaking code. NCAR
> > and the DOE ParVis project, in particular, has a very large Swift
> > script that they are testing for production use, and we really dont
> > want that to break.
> >
> > e should not allow 0.93 to break current user code -- if at all
> > possible.
> 
> On one hand, I agree with you.
> 
> On the other hand, I do not think that backwards compatibility, in the
> long run, is a good justification for keeping something that is really
> poorly done.

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