> From: peter reilly [mailto:[EMAIL PROTECTED]
>
>
> >
> > Property interceptors are not part of Ant, and might never
> be for that
> > matter. Using a notation that mimicks interceptors is
> probably not a
> > good idea either.
> >
> > As I've been saying all along, lets just introduce a new (unique)
> > notion for attribute/variable expansion (at use time rather than
> > definition time), which is something new in Ant anyhow. No
> (or less?)
> > backward compatibility issues, and makes it plain and
> obvious what is
> > what:
> >
> > ${name} it's a property!
> > (@name) it's an attribute/variable!!!
>
> yes but (IMO) this is confusingly similar to XPath use of variables.
> <macrodef name="cut">
> <attribute name="use">
> <sequential>
> <xmltask source="input.xml" dest="1.xml >
> <cut path="web/servlet/context/[EMAIL PROTECTED]'(@use)']"
> buffer="storedXml" />
> </xmltask>
> </sequential>
> </macrodef>
>
This to me is the best argument for using ${...} as the only
syntax for variables. If not, people will not only need to
learn a new syntax but also we need to create a way to escape
the meaning of the syntax, as per the example above.
We have already gone through all the pain of devicing and recognizing
escape sequences for the syntax for properties, we do not need to
go through that again. Lets keep things simple for users.
Jose Alberto
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
