> > Thinking about it, 'dynamic properties' is probably the wrong term for us
> > to use. I think we're actually after a way to statically declare additional
> > properties and methods for domain objects. I use 'static' in the sense that
> > one can infer from the build language that these properties exist and are
> > usable in the build script, without having to actually run the build script.
> > For example, the declarative statement: apply plugin: 'java' infers that the
> > project has a 'sourceCompatibility' property. Or that there is a 'runtime'
> > configuration, and so on. You don't need to run the build script to know
> > this.
Rather than say: "dynamic properties",
how about this: "computed properties"
Reason:
The term "computed properties" implies:
(1) The property value is not hard-coded
(yet it does not imply mutable once set).
(2) The past tense.
This is appropriate because when you're inside an
task action, the computation has been completed
(it happened prior to the topological sort of dependencies).
Cheers,
-Jon
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
