Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 41476 invoked from network); 21 Jun 2004 15:41:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 21 Jun 2004 15:41:46 -0000 Received: (qmail 3283 invoked by uid 500); 21 Jun 2004 15:41:52 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 3218 invoked by uid 500); 21 Jun 2004 15:41:51 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 3201 invoked by uid 99); 21 Jun 2004 15:41:51 -0000 Received: from [66.180.124.162] (HELO central.purematrix.com) (66.180.124.162) by apache.org (qpsmtpd/0.27.1) with ESMTP; Mon, 21 Jun 2004 08:41:51 -0700 Received: from purematrix.com (slip-32-103-218-112.co.us.prserv.net [32.103.218.112]) by central.purematrix.com (Postfix) with SMTP id A38CC3E59; Mon, 21 Jun 2004 09:41:34 -0600 (MDT) Sender: jax@purematrix.com Message-ID: <40D70161.805ED1A4@purematrix.com> Date: Mon, 21 Jun 2004 09:40:17 -0600 From: "Jack J. Woehr" X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.9 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Ant Developers List Subject: Re: and local References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Stefan Bodewig wrote: > On Mon, 21 Jun 2004, Jose Alberto Fernandez > wrote: > >> From: Stefan Bodewig [mailto:bodewig@apache.org] > > > >> The main limitation I see without local properties in is > >> when your macro uses a property setting task like or > >> - you currently need to provide a unique property name > >> to those tasks if you want to reuse the macro. > > > > Is this really the only reason, currently, for local properties? > > Not the only, but a very important one. > > > Because if that is the case, maybe we can solve the problem in a > > completely different way, which is specific to . > > What you describe is pretty much what I (and probably anybody else) > use as a workaround. I create what would be a local property by using > a name contains the name of at least one of the task's attributes. It seems to me that if someone really needs this sort of thing, then the use of Ant-Contrib's Variable is pretty much sufficient, esp. if property parsing becomes recursive (e.g., per the patch I submitted already) so that you can access properties via a second-level indirection. Would one then still need locals? If absolutely necessary, a GenUniquePropertyName task could be coded. -- Jack J. Woehr # We have gone from the horse and buggy Senior Consultant # to the moon rocket in one lifetime, but Purematrix, Inc. # there has not been a corresponding moral www.purematrix.com # growth in mankind. - Dwight D. Eisenhower --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org