Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 33490 invoked from network); 11 Jul 2002 14:19:32 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 11 Jul 2002 14:19:32 -0000 Received: (qmail 6128 invoked by uid 97); 11 Jul 2002 14:19:44 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 6112 invoked by uid 97); 11 Jul 2002 14:19:44 -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 6079 invoked by uid 98); 11 Jul 2002 14:19:43 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) To: "Ant Developers List" Subject: Re: enhancement, it's done, but do you like how it works? MIME-Version: 1.0 X-Mailer: Lotus Notes Build V60_M13_04302002 Pre-release 2 April 30, 2002 From: dion@multitask.com.au Message-ID: Date: Fri, 12 Jul 2002 00:33:28 +1000 X-MIMETrack: Serialize by Router on gateway/Multitask Consulting/AU(Release 5.0.8 |June 18, 2001) at 07/12/2002 12:33:33 AM, Serialize complete at 07/12/2002 12:33:33 AM Content-Type: multipart/alternative; boundary="=_alternative 004D79F04A256BF3_=" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N --=_alternative 004D79F04A256BF3_= Content-Type: text/plain; charset="US-ASCII" Jose Alberto Fernandez wrote on 07/11/2002 11:45:23 PM: > I see no reason why you need to consider "super" as > special, from the point of view of the ANT engine. The > implementation just needs to do a syntactic rewrite. Yes, but it means something in particular. It's 'magic' for "call the replaced target". Magic != intuitive. > You ask about backward compatibility. I see no > compatibility issue at all. If you have targets called > "supper.XXXXX" they are just there. So what gets called if I already have a target in the build file called 'super.XXXX'? What does the antcall do? Call the one that existed in my build file, or the 'replaced' target? Or both? > If you have "super.XXXX" and "XXXX" there is no issue > either. > > If you import such a buildfile into another AND > redefine "XXXX", then the rewriting rule will renamed > the original "XXXX" to "super.XXXX" which should cause > a parsing error since you have two targets with the > same name (just as it complains today). Which would be unnecessary if the magic 'super' didn't exist tho.... > Is this a backward compatibility issue? NO. In this > situation you are modifying the build, directly or > indirectly. Backward compatibility only means that old > buildfiles have to keep on running as intended. > It does not mean that I can start using anything new > and not have to change something. So once I start using a new feature of Ant 1.6, it's ok for my old build files to stop running as they used to? [snip] > depends="${ant::super(mytarget)}"> > > > > now, I doubt anybody has a property called like that. Yep, and I'll be stunned if anybody gets it right first time :) > comments, I'd much rather stick with import and include as XSL defines them. Clearer, consistent with other technologies, and no messy super.stuff to be done. > Jose Alberto -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers --=_alternative 004D79F04A256BF3_=--