Hi, gang!
LSU> Are there any other issues besides the ones listed
LSU> by Aaron? That is:
LSU>
LSU> a) Where does it belong?
LSU> b) Should MutableConfiguration extend
LSU> Configuration?
Yes. Three more issues.
A.
addChild( Configuration other )
addAll( Configuration other )
addAllChildren( Configuration other )
should receive deep-copy semantics (unlike DefaultConfiguration)
B.
interface MutableConfiguration
{
/**
* Create a MutableConfiguration instance
* of the appropriate class and put to the
* list of children
*/
MutableConfiguration createChild( String name );
}
C.
Do we have
getChildCount()
getChild( int no )
getChild( String name )
methods in Configuration?
If no, I will ask to add them.
And likewise in MutableConfiguration I'd like
interface MutableConfiguration
{
MutableConfiguration getMutableChild( int no );
MutableConfiguration getMutableChild( String name );
}
or
interface ConfigurationMutator
{
int getChildCount();
ConfigurationMutator getChild( int no );
ConfigurationMutator getChild( String name );
}
I just have an aneasy feeling about methods returning arrays -
feel sorry about arrays being allocated. I'm not against these
methods, just want methods for accessing children one-by-one
also.
Cheers, Anton
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
