Return-Path: Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 50249 invoked by uid 500); 20 Aug 2003 15:25:56 -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 50017 invoked from network); 20 Aug 2003 15:25:47 -0000 Received: from unknown (HELO olinexvs01.olin.edu) (4.21.173.2) by daedalus.apache.org with SMTP; 20 Aug 2003 15:25:47 -0000 Received: from olinexfe01.olin.edu ([10.1.15.93]) by olinexvs01.olin.edu with Microsoft SMTPSVC(5.0.2195.6713); Wed, 20 Aug 2003 11:25:34 -0400 Received: from cognition.olin.edu ([4.36.33.205]) by olinexfe01.olin.edu (SAVSMTP 3.0.0.44) with SMTP id M2003082011253319238 for ; Wed, 20 Aug 2003 11:25:34 -0400 Message-ID: <3F439159.6090600@cognition.olin.edu> Date: Wed, 20 Aug 2003 11:18:49 -0400 From: Gus Heck User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ant Developers List Subject: Re: [new tasks] presetdef and macrodef References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 20 Aug 2003 15:25:34.0834 (UTC) FILETIME=[4CEEAD20:01C3672F] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > > >I stopped arguing this point, as I was the only one concerned apparently, >but since Jose Alberto brings it up again... > >Having ${NAME} not evaluate to the value, if any, of the NAME property, at >the time the task it's used in ( is this case) is executed, is >REALLY REALLY BAD in my sincere opinion. Maybe does it, but that > > > I agree with you on this... I had to use foreach for the first time recently and was astounded that it had been written that way. It completely confuses the issue of property immutability, and makes the parameter hard to find. You need to know what the argument is before you look for it. Think about explaining property imutability to someone... ${foo.bar} can never change... exept when it isn't a property... "how do I know it isn't a property?" they ask... The answer would be you just have to know the tasks where ${foo.bar} might not be a property, and check what the parameter name is. At that point the person you are explaining this to rolls their eyes and says "Ugh. That is annoying" :) I think macrodef should not duplicate this problem and if foreach ever came into ant it should have a namechange and new parameter system. -Gus --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org