Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 31959 invoked from network); 21 Apr 2000 12:49:54 -0000 Received: from mercury.sun.com (192.9.25.1) by locus.apache.org with SMTP; 21 Apr 2000 12:49:54 -0000 Received: from shorter.eng.sun.com ([129.144.124.35]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA28238 for ; Fri, 21 Apr 2000 05:49:54 -0700 (PDT) Received: from eng.sun.com (pra-rem-8.Czech.Sun.COM [129.156.75.109]) by shorter.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id FAA29131 for ; Fri, 21 Apr 2000 05:49:47 -0700 (PDT) Message-ID: <38FFBD97.2EC7C300@eng.sun.com> Date: Thu, 20 Apr 2000 19:31:51 -0700 From: James Duncan Davidson X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; I) X-Accept-Language: en MIME-Version: 1.0 To: ant-dev@jakarta.apache.org Subject: Re: Ant Principles References: <852568C6.00212757.00@d54mta04.raleigh.ibm.com> <38FD6EA9.CAE5A02D@eng.sun.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > But in doing so, you've proposed: > > style -- String defaults > file -- rich file type, defined with a string > > I'm not sure that the extra typing given this way is worth not just > calling them properties and throwing out the ${...} usage. So, I haven't yet seen your response (off-line), but as I work through a draft of the document, I can see where you'd need typing of this nature. properties = just strings, could be cast to proper types style = default setting for element attribs that aren't set. Can be cast to proper type filedef = file definition, can be used in script as The one thing they all have is a name key, this would allow them to be mixed on property settings as they come in on the command line, etc. So, let's look at use cases.... (thinking aloud)