Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ant-dev@jakarta.apache.org
To: ant-dev@jakarta.apache.org
Subject: Re: Converter Area of Concern
References: <67FE02381F67D3119F960008C7845A2C0565AB37@nt_syd_ex09.macbank>
From: Stefan Bodewig <bodewig@apache.org>
Date: 31 May 2001 14:02:20 +0200
In-Reply-To: Tim Vernum's message of "Thu, 31 May 2001 20:21:09 +1000"
Message-ID: <m3itihd8vn.fsf@bodewig.bost.de>
Lines: 22
User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Cuyahoga Valley)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Tim Vernum <Tim.Vernum@macquarie.com.au> wrote:

> From: Stefan Bodewig [mailto:bodewig@apache.org]
> 
>> >>Not entirely, at least for the two interpretations I've given,
>> >>they belong to (2) as well.  If I define a new task/type, I may
>> >>need a custom converter.
>> > 
>> > Possibly but should we allow/encourage that sort of action?
>> 
>> How would I use my new data type if I cannot supply a converter for
>> the ${} expansion of it?  Yes, I think we should allow that.
> 
> What sort of data-types are people likely to use?

I have no idea, just don't want to restrict them when it is not really
necessary.

List of hostnames to ping, ftp files from, do http gets on. List of
email addresses ...

Stefan