Return-Path: 
 <dev-return-52812-apmail-ant-dev-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-dev-archive@www.apache.org
Received: (qmail 4616 invoked from network); 11 Nov 2003 19:02:37 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 11 Nov 2003 19:02:37 -0000
Received: (qmail 37243 invoked by uid 500); 11 Nov 2003 19:02:12 -0000
Delivered-To: apmail-ant-dev-archive@ant.apache.org
Received: (qmail 37177 invoked by uid 500); 11 Nov 2003 19:02:12 -0000
Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@ant.apache.org>
List-Subscribe: <mailto:dev-subscribe@ant.apache.org>
List-Help: <mailto:dev-help@ant.apache.org>
List-Post: <mailto:dev@ant.apache.org>
List-Id: "Ant Developers List" <dev.ant.apache.org>
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Delivered-To: mailing list dev@ant.apache.org
Received: (qmail 37088 invoked from network); 11 Nov 2003 19:02:11 -0000
Received: from unknown (HELO london.cellectivity.com) (212.18.242.163)
  by daedalus.apache.org with SMTP; 11 Nov 2003 19:02:11 -0000
content-class: urn:content-classes:message
Subject: RE: macrodef - do attributes as properties or substitutions
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 11 Nov 2003 19:01:47 -0000
Message-ID: <747F247264ECE34CA60E323FEF0CCC0C0F5162@london.cellectivity.com>
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: macrodef - do attributes as properties or substitutions
Thread-Index: AcOoTo71bGyKieZ3RIattZ899g3AngAJCYCAAANCVLAAAP5vQA==
From: "Jose Alberto Fernandez" <jalberto@cellectivity.com>
To: "Ant Developers List" <dev@ant.apache.org>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

> From: Steve Cohen [mailto:SCohen@sportvision.com]=20
>=20
> Wouldn't you say, though, Jose, that <macrodef> does replace=20
> those uses of <antcall> for which <antcall> had too big a=20
> footprint for the job? =20
>=20

Oh, but of course. I do plan to use macrodef to replace things
that I did with <antcall> before. But the reason they were done
with <antcall> before, is that it was more convinient than writing
the equivalent script or java code; they did not need to evaluate
multiple targets or other complex stuff.=20

For things more complex, <antcall> is still the way to go. Why?
Because it provides a new execution context, in which I can deside
whether properties are inherited or not, and it provides isolation
so that the parent context is not directly manipulated by the child.

<macrodef> using <local> would be a cluge in the middle, half here
half there, which I think is wrong. Either is a macro definition=20
(as the term is defined in computer science form the days of assembler)
it should be called something else and have a real execution context.

BTW, how this things will affect the other tasks derived from macrodef
like presetdef?


Jose Alberto

> -----Original Message-----
> From: Jose Alberto Fernandez [mailto:jalberto@cellectivity.com]=20
> Sent: Tuesday, November 11, 2003 11:19 AM
> To: Ant Developers List
> Subject: RE: macrodef - do attributes as properties or substitutions
>=20
>=20
> I think I need to justify some more what do I think the way I=20
> do about macrodef. I know the vote is already going, but I=20
> really want for people to understand my position.
>=20
> To me macrodefs are for writing all those tasks that I am too=20
> lazy, or they are too simple for me to need to go and write=20
> and maintain some Java code. It is not to replace <antcall/>=20
> but as a side efect, it will replace all those little=20
> antcalls we wrote=20
> because we didn't want to write java.
>=20
> With that in mind, I would want <macrodef> to resemble a Java=20
> task and not to resemble <ant(call)>. And if it resemples a=20
> java task, then attributes should resemble java variables in my code.=20
> That is, its values should not affect the values of=20
> properties (which is what <local> does). If I want a task to=20
> affect other tasks then I can always call <property> or=20
> <local> as part of the macro. But if <atributes> modify=20
> properties, then there is no way for me to stop them for happening.
>=20
> Substitution is the least interfearing behavior.
>=20
> So, that is why I think the way I do. Comments? changes of votes? :-)
>=20
> Jose Alberto
> =20
> > -----Original Message-----
> > From: Stefan Bodewig [mailto:bodewig@apache.org]
> > Sent: 11 November 2003 12:23
> > To: dev@ant.apache.org
> > Subject: [VOTE] macrodef - do attributes as properties or
> > substitutions
> >=20
> >=20
> > Hi,
> >=20
> > I don't think that another discussion thread will lead us anywhere.=20
> > Instead of trying to summarize what has been discussed, let=20
> me point=20
> > to the archives (I hope the list is complete):
> >=20
> <http://marc.theaimsgroup.com/?t=3D106085269000002&r=3D1&w=3D2>
> <http://marc.theaimsgroup.com/?t=3D106633643100003&r=3D1&w=3D2>
> <http://marc.theaimsgroup.com/?t=3D106675058100005&r=3D1&w=3D2>
> <http://marc.theaimsgroup.com/?t=3D106639175600004&r=3D1&w=3D2>
> <http://marc.theaimsgroup.com/?t=3D106672947100005&r=3D1&w=3D2>
> <http://marc.theaimsgroup.com/?t=3D106720903000001&r=3D1&w=3D2>
> <http://marc.theaimsgroup.com/?t=3D106761809300003&r=3D1&w=3D2>
>=20
> I'd like to keep this particular vote focussed on property=20
> versus textual substitution.  I am aware that the vote won't=20
> be complete after that as we'll still have issues to decide=20
> upon (scope+extent or notation, depending on this vote's=20
> outcome), but let's get this one here straight first.
>=20
> Actually, I'm not 100% sure about the rules we have to apply=20
> since we've already shipped betas with the code, so strictly=20
> speaking a decision we are considering a code change which=20
> would require (lazy) consensus of the committers as opposed=20
> to a new idea that would require a majority only.  Let's see=20
> where we get from here and whether we'll have to actually=20
> decide that at all 8-)
>=20
> Stefan
>=20
> OK, how do we want to implement <macrodef> attributes:
>=20
> [ ] as textual substitution
> [ ] as "real" Ant properties
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>=20
>=20

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org