Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 88943 invoked from network); 19 Feb 2002 11:33:23 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 19 Feb 2002 11:33:23 -0000 Received: (qmail 9626 invoked by uid 97); 19 Feb 2002 11:33:20 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 9569 invoked by uid 97); 19 Feb 2002 11:33:20 -0000 Mailing-List: contact ant-dev-help@jakarta.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 ant-dev@jakarta.apache.org Received: (qmail 9543 invoked from network); 19 Feb 2002 11:33:19 -0000 Message-ID: <20020219113319.96587.qmail@web10806.mail.yahoo.com> Date: Tue, 19 Feb 2002 11:33:19 +0000 (GMT) From: =?iso-8859-1?q?Jose=20Alberto=20Fernandez?= Subject: Re: antlib descriptor To: Ant Developers List In-Reply-To: <200202191044.g1JAiKU28416@mail004.syd.optusnet.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N --- Peter Donald wrote: > On Tue, 19 Feb 2002 18:03, Jose Alberto Fernandez > wrote: > > Anything that we may declare is a type (well > except for the thing > > that actually defines new types). I did not think > was worth segregating > > this one from the others. > > I suspect he wants to support the notion of roles > (ie categories of types > that implement an interface) in the same descriptor. I already support the notion of roles without need for segregating things around. If you want to look it that way, the only predefined "role" is 'role' itself. The implementation is not treating it this way at the moment, but in principle a role is just a predefined type in the system as anything else. Hummm, maybe I should just do that and make the whole code even more general. No stinking string constants. :-) Let me just sumarize what my DTD currently is for and then how it could be reduced for this firts integration: Here "[typename]" correspond to the name of a role previously made available in the system. At this point I am programatically predefining two typenames: "task" and "datatype". I do not have any attachment to these names so I have no issue on changing them. The DTD I think we should stride for would be limited as follows: Again no attachment to names although I prefer "class" to "classname" as I prefer shorter names. __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To unsubscribe, e-mail: For additional commands, e-mail: