ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Cohen" <SCo...@sportvision.com>
Subject RE: [VOTE] macrodef - do attributes as properties or substitutions
Date Mon, 17 Nov 2003 18:50:10 GMT
Another non committer here.
I don't like $(x) because it looks too much like ${x}, although I
suppose I could get used to that.  Therfore, I am drawn to
@{x}.  ${attribute:x} is possible but way too much typing for my taste.
Abbreviated to ${att:x} or ${attrib:x} my negativity level goes down
accordingly.

Before "voting", though, could someone list all the conflicting usages
with other systems that ant must interface with.

-----Original Message-----
From: peter reilly [mailto:peter.reilly@corvil.com] 
Sent: Monday, November 17, 2003 12:10 PM
To: Ant Developers List
Subject: Re: [VOTE] macrodef - do attributes as properties or
substitutions


OK, how do we want to implement <macrodef> attributes:
                                  current
 [ ] as textual substitution    ~ 4
 [ ] as "real" Ant properties   ~ 2

undecided                       ~ 1

If macrodef attribute are to be implements as substitutions, what should
be the notation? (where x is the attribute name)

 [ ] as ${x} (look like ant properties)
 [ ] as $(x) 
 [ ] as @x
 [ ] as ${attribute:x}
 [ ] as @{x}
 [ ] some thing else



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


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


Mime
View raw message