I would rather have Jose's idea of a <local-property/> task. This could be used outside of macrodef.
The only problem is the implementation. Peter On Friday 17 October 2003 17:02, Shatzer, Larry wrote: > Maybe allow <attribute> have another <attribute> that allows it to be > undeclared with default or passed in, so we can set it inside the macrodef, > such as "newcurrent". > > Example: > > <macrodef name="recursive"> > <attribute name="until"/> > <attribute name="current"/> > <attribute name="method"/> > <attribute name="newcurrent" staticscope="true"/> > ... > </macrodef> > > Then when you call "recursive" such as this: <recursive until="10" > current="0" method="blah"/> it won't die that you did not pass > "newcurrent". > > the "staticscope" attribute name could be something else, or scope="static" > and a list of others that could be used. > > -- Larry > > > -----Original Message----- > > From: peter reilly [mailto:[EMAIL PROTECTED] > > Sent: Friday, October 17, 2003 12:43 AM > > To: Ant Developers List > > Subject: Re: Macrodef and parallel in a recursive situation > > > > > > The parellel would cause grief. > > The problem is not the attribute, I think > > but the "newcurrent" global "variable". > > > > On using macrodef, I have noticed that > > it would be really cool to have a static scopped > > variable. > > > > Peter > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
