ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jose Alberto Fernandez" <j_a_fernan...@yahoo.com>
Subject Re: [PATCH] PropertyCopy and Foreach (NEW OPTIONAL TASKS)
Date Tue, 25 Sep 2001 14:24:54 GMT
Ant is not a Scripting/Programming tool. It expresses in a declarative fashion the way to build
something. You do not specify the total order of all targets. It is upto ANT's dependecy engine
to decide the order of execution as long as dependencies are preserved. There is no reason
why FOREACH should work any different. If the iterations are computed based on <fileset>
or some other, then we need to be aware that such constructs are SETS and such there is no
order associated with its elements. And there is little way to guarantee that it will be iterated
in the sameorder on every OS that may ever exists.

Jose Alberto

From: "Matthew Inger" <matti@sedonacorp.com>

> I think that not guaranteeing the order of
> a foreach task is a very bad thing.  It's
> a scripting/programming style task, and people
> are used to it executing in a defined order,
> and to change that at some later date would
> produced behavior that some might not expect.
> 
> On Tue, 2001-09-25 at 04:00, Stefan Bodewig wrote:
> > On 21 Sep 2001, Matthew Inger <matti@sedonacorp.com> wrote:
> > 
> > > But to be so blind as to not even open the possibility of including
> > > it as part of the optional tasks is silly, from my point of view.
> > 
> > I agree with you - or at least I would if there was an optional
> > package that doesn't impose additional maintenance burden on the Ant
> > committers.  As things are now, we have no way to give people commit
> > access to just a single source file - so every modification to a
> > contributed task takes some time for one of the committers to pick it
> > up.  Ask Les Hughes about his contributions in the Perforce area to
> > see what that means.
> > 
> > When you look through the stuff for Ant2, you'll see that we want to
> > make extending Ant a lot easier than it is right now - with the
> > concept of task libraries I guess custom tasks from external sources
> > will become more common than they are right now.
> > 
> > As for SourceForge-ing an ant-contrib module - go ahead.  I don't know
> > what has happened to taskdefs.org, though.  I wouldn't use
> > org.apache.tools.ant as base package but org.apache.ant BTW - this is
> > where Ant2 is going to live (once it is going to be alive).  
> > 
> > Who would decide what goes into this module - whom am I going to ask
> > if I want to contribute my IfTask? 8-)
> > 
> > Finally on the subject of a foreach task, I'd recommend to simply rely
> > on TaskContainer for the "task embedding" part and to not guarantee
> > the order of execution so you are free to change the implementation as
> > Ant's core evolves (or even throw in parallel execution of the "foreach"
> > block for different arguments).
> > 
> > Stefan
> -- 
> Matt Inger (matt.inger@sedonacorp.com)
> Sedona Corporation
> 455 S. Gulph Road, Suite 300
> King of Prussia, PA 19406
> (484) 679-2213
> "Self-respect - the secure feeling that no one,
>  as yet, is suspicious." -H.L. Mencken 
> 


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


Mime
View raw message