Am I the only person that thinks conditional flow control using XML is just a Bad Thing(tm)? Flow control == processing and we already have excellent processing languages.
A target is a "piece of work". If that piece of work depends on other pieces of work, we define that in dependencies. Everything in this design is pass/fail, Like a transaction. If/unless attempts to add a tiered conditional process tree on top of this pass/fail concept. This is not what a target (or should I say *my* opinion of what a target) should be. If the desire is so strong for Ant to be a cross-platform build scripting language, why can't we just implement a subset of Python for Ant2 and quit trying to kludge scripting into XML? MrT > -----Original Message----- > From: Daniel Barclay [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 15, 2001 11:23 AM > To: [EMAIL PROTECTED] > Subject: Re: if and unless attributes for all Tasks > > > Peter Donald wrote: > > > > At 01:04 14/5/01 -0400, Daniel Barclay wrote: > > >> If you need it, wrap it in a target. > > > > > >That won't work well if you want different tasks within one target > > >to have different conditions. > > > > If you have that then you misunderstand the notion of targets ;) > > I don't think so, but what you do mean? > > You don't think one might want to configure how a target is executed > by parameterizing tasks with boolean values similarly to how we > parameterize tasks with string values? > > Daniel > -- > Daniel Barclay > Digital Focus > [EMAIL PROTECTED] >
