On 12/6/00 11:18 PM, "Peter Donald" <[EMAIL PROTECTED]> wrote:
> Why ? You would prefer for ${fred} to potentially mean 7-8 different things
> depending on where it is used. Currently we do that with different
> namespace for filesets/properties/other datatypes. I prefer simplicty over
> complexity that you seem to be advocating ?
Same thing exists with System.properties. "fred" means very different things
when it is the result of "user.dir" or "home.dir" or "user.name". Context
matters. I really don't see this as complexity that I'm advocating. Adding a
bunch of typing on top of this is complex afaic.
Filesets != properties. A property is a simple name=value pair. Filesets is
a one-to-set mapping of files which may contain regexp patterns.
> There has been a lot of feedback on that issue. A lot of people did not
> like that behaviour would silently fail because they mistyped a property
> name. Even ant had mis-typed property names at one stage ;)
The same thing can happen in any data file.. A mistyped property key in a
java.util.Properties list exhibits this behavior -- as does a mistyped
attribute name in a XML file that isn't being validated against a DTD. This
is not a problem that is unique to Ant, and yet we're fine with it in those
cases.
--
James Duncan Davidson [EMAIL PROTECTED]
!try; do()
