From dev-return-50165-apmail-ant-dev-archive=ant.apache.org@ant.apache.org Tue Sep 02 07:24:41 2003 Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 7633 invoked from network); 2 Sep 2003 07:24:41 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 2 Sep 2003 07:24:41 -0000 Received: (qmail 58582 invoked by uid 500); 2 Sep 2003 07:24:12 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 58451 invoked by uid 500); 2 Sep 2003 07:24:10 -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 58434 invoked from network); 2 Sep 2003 07:24:10 -0000 Received: from unknown (HELO main.gmane.org) (80.91.224.249) by daedalus.apache.org with SMTP; 2 Sep 2003 07:24:10 -0000 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19u5Wl-0006G2-00 for ; Tue, 02 Sep 2003 09:24:35 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: dev@ant.apache.org Received: from sea.gmane.org ([80.91.224.252]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19u5Wk-0006Fu-00 for ; Tue, 02 Sep 2003 09:24:34 +0200 Received: from news by sea.gmane.org with local (Exim 3.35 #1 (Debian)) id 19u5WB-0007Vg-00 for ; Tue, 02 Sep 2003 09:23:59 +0200 From: "Knut Wannheden" Subject: Re: Getting 1.6 out the door Date: Tue, 2 Sep 2003 09:23:59 +0200 Lines: 38 Message-ID: References: Reply-To: "Knut Wannheden" X-Complaints-To: usenet@sea.gmane.org X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Sender: news X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N > > > 3. and > > > > > a) resolution of properties > > The issue here is that properties get resolved when the > > macro is used and not when the macro is defined. > > I think that it would be difficult to resolve the > > properties correctly when the macro is defined. > > > > I think that the current implementation and behaviour is > > preferable. > > I think it's sad that you reflect on this from the implementation > perspective rather than the user's one... One of the major 'feature' > of Ant is that it is very explicit and relatively simple. > > It's not all about power, or one would use a real programming language > like Perl or Python. , although powerful, complexifies the rules > of Ant, namely the property expansion one, making it context dependent! > > Never underestimate the power and simplicity of context/scope free rules. > Although Ant already has scopes with //, the property > expansion rules works the same everywhere, and I'd like this to stay the > same. > Of course you always have to remember that this property expansion doesn't work the same for targets. Inside a target the properties aren't expanded until the target is called. This may seem obvious, but now that any task can be at the top-level, a target doesn't feel that different from a task. It's a task container and in a way not that different from . Just my $0.02. -- knut --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org