Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
To: ant-dev@jakarta.apache.org
Subject: Re: Call for patches
References: <852568E8.000E9872.00@d54mta04.raleigh.ibm.com>
	<013001bfc4ad$35d374e0$b41c063e@eddie>
	<001301bfc4be$115b7520$b4ed5c18@twcny.rr.com>
From: Stefan Bodewig <bodewig@bost.de>
Date: 23 May 2000 17:01:31 +0200
In-Reply-To: "Bill Barnhill"'s message of "Tue, 23 May 2000 09:51:59 -0400"
Message-ID: <m3zoph71kk.fsf@sbodewig.bost.de>
Lines: 30
User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Canyonlands)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

>>>>> "BB" == Bill Barnhill <bbarnhil@twcny.rr.com> writes:

 BB> Instead of multiple if's, it is a task called availablelist
 BB> which takes paramters classes, resources, and files, each of
 BB> which are plural versions of the class, resource, and file
 BB> parameters of the available task.

I'd prefer a solution like this as it wouldn't require a change to
Ant's core but merely add a task. 

But wouldn't it be better to extend the functionality of available
instead of adding a new task with overlapping concerns?

As for the notavailablelist task you describe in a different mail, you
explicitely say this is not the opposite of availablelist so the name
is kind of misleading. What I gather from your description:

* All resources are there => avalailablelist is true, notavailablelist
is false.

* None of the resources are there => avalailablelist is false,
notavailablelist is true.

* Any one of the resources is there but not all of them => both
availablelist and notavailablelist are false.

This makes for powerfull combinations but looks tricky (read as needs
a bunch of good documentation to match the simplicity goal).

Stefan