On Sat, 9 Feb 2002 12:49, Adam Murdoch wrote: > > On Sat, 9 Feb 2002 09:33, Adam Murdoch wrote: > > > > * Uses the DataType role when creating instances for interface > > > > properties, > > > > rather than using the interface itself as the role. > > > > > > The motivation for this change was to allow a data type to be used in > > > , TypeInstanceTask, and as a parameter to add() methods. > > > > Im not sure I follow you here. If I have a > > > > add( MyRole value ); > > > > will that look up in the registry under MyRole or DataType? > > DataType. Same as and TypeInstanceTask. I still don't understand the motivation for this. Instead of MyRole lets say interface Condition extends DataType {} add( Condition c ); Why would you want to look up an arbitrary DataType? Wouldn't it be best to just look up types that implement Condition? > > If it is looking > > up the registry under DataType - what happens in the following case > > > > > > > > > > > > > > > > Both types have the same name but different roles. So what would > > happen here ? > > Not sure whether you're asking about 2 classes or one single class here? 2 different classes - ie > > > > BTW I noticed you removed the > > > > myException.fillInStackTrace() when exceptions were rethrown - > > what was the > > motivation for that? > > Laziness (my primary motivation :) excellent! > - so that the original stack trace was > there for me to click on in IDEA. I can put it back if you like. No need for now. When re start stabilizing and releasing to the public it will be good to go back and do it though. -- Cheers, Pete *------------------------------------------------* | Trying is the first step to failure. | | So never try, Lisa - Homer Jay Simpson | *------------------------------------------------* -- To unsubscribe, e-mail: For additional commands, e-mail: