ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: [PATCH] Inheriting properties from a parent project (Project .java ,,
Date Mon, 17 Jul 2000 13:28:12 GMT

I used a Properties object because it got me what I wanted - inherited
properties with a minimum of fuss.  The current idea of properties is still
String based - getProperty coerces to a String.  Untill the new framework
comes around, that's what everyone's code is expecting.

Here's a suggestion.  I create a ProjectProperties class that uses a
Hashtable as its backing store, and will do the recursive getProperty call
but return an Object instead of a String.  The Project.getProperty method
casts to a String the same way it does now.  When we move to richer
property objects, the support is already there, and I get the memory
savings I need.

How does that sound?

Glenn McAllister
TID - Software Developer - VisualAge for Java
IBM Toronto Lab, (416) 448-3805
"An approximate answer to the right question is better than the
right answer to the wrong question." - John W. Tukey

Please respond to

Subject:        Re: [PATCH] Inheriting properties from a parent project
( ,,

>>>>> "g" == glennm  <> writes:

 g> This patch introduces the concept of a parent project, and the use
g> of java.util.Properties to hold the property lists, rather than a
g> Hashtable.

While I understand the need for the first I don't see why you've
introduced the second - especially since we want to move away from
String based properties.


View raw message