Return-Path: 
 <dev-return-58802-apmail-ant-dev-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-dev-archive@www.apache.org
Received: (qmail 55854 invoked from network); 23 Jun 2004 16:24:15 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 23 Jun 2004 16:24:14 -0000
Received: (qmail 43706 invoked by uid 500); 23 Jun 2004 16:23:41 -0000
Delivered-To: apmail-ant-dev-archive@ant.apache.org
Received: (qmail 43508 invoked by uid 500); 23 Jun 2004 16:23:39 -0000
Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@ant.apache.org>
List-Subscribe: <mailto:dev-subscribe@ant.apache.org>
List-Help: <mailto:dev-help@ant.apache.org>
List-Post: <mailto:dev@ant.apache.org>
List-Id: "Ant Developers List" <dev.ant.apache.org>
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Delivered-To: mailing list dev@ant.apache.org
Received: (qmail 43335 invoked by uid 99); 23 Jun 2004 16:23:37 -0000
Received: from [213.94.219.177] (HELO corvil.com) (213.94.219.177)
  by apache.org (qpsmtpd/0.27.1) with ESMTP; Wed, 23 Jun 2004 09:23:37 -0700
Received: from [172.18.1.171] (angel.local.corvil.com [172.18.1.171])
	by corvil.com (8.12.9/8.12.5) with ESMTP id i5NGNEOC088367
	for <dev@ant.apache.org>; Wed, 23 Jun 2004 17:23:15 +0100 (IST)
	(envelope-from peter.reilly@corvil.com)
Message-ID: <40D9AE94.1000205@corvil.com>
Date: Wed, 23 Jun 2004 17:23:48 +0100
From: Peter Reilly <peter.reilly@corvil.com>
User-Agent: Mozilla Thunderbird 0.6 (X11/20040502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ant Developers List <dev@ant.apache.org>
Subject: Re: <macrodef> and local
References: <BAY2-DAV16PZrIkyPzG00005f86@hotmail.com>
In-Reply-To: <BAY2-DAV16PZrIkyPzG00005f86@hotmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

It is not only with macrodef's that folk want "if/unless", but
macrodef is a bit more obvious because of it's use as a replacement for
<antcall> used as a sub-routine.

Using constructed property names is a good work-around for
the lack of local properties. But it is a work-around, and there
are some cases where true local properties would be more easily
be used.

The <break> task is interesting. I am concerned however about
how third party task containers would work with it.

Peter

Magesh Umasankar wrote:

>From:       Matt Benson <gudnabrsam () yahoo ! com>
>Date:       2004-06-23 15:02:54
>
>  
>
>>I cringe at the thought of the number of "unique
>>properties" that could be floating about resulting
>>from this...
>>    
>>
>
>Is the user community complaining?  The only issue
>that seems to come up every now and then is lack of 
>straight-forward support like if/unless/depends on 
>macrodef and I'd like to see us address that.  I haven't
>seen a real-world use-case where the only way to
>solve an issue is by using locals inside macrodef.
>
>Hijacking the topic a bit...
>
>Instead of adding if & unless attributes to macrodef, 
>I suggest adding a new task <break> that can be placed
>at arbitrary locations inside a task container to stop
>further tasks in that container from executing.  Cleaner
>compared to if/then/else constructs and is not tied to 
>macrodef alone.
>
><break> is smiliar to <fail> except that it re-routes
>control to the next task container instead of totally
>stopping the build process.
>
>  
>
>>-Matt
>>    
>>
>
>Cheers,
>Magesh
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>For additional commands, e-mail: dev-help@ant.apache.org
>
>
>
>  
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org