Re: How to decide which implementation to use?

Take a step back. Do you really need to build something this abstract? If it's so abstract that you're unable to answer simple questions about how it should behave that's a good hint that it's too abstract to be useful.

Well-designed OO systems speak the language of their problem domain. Assuming the problems you're trying to solve don't involve "kernels" (of corn?) and "agents" (007?), you're probably heading too far into abstract implementation, in my opinion.

-sam

Comment on Re: How to decide which implementation to use?

Replies are listed 'Best First'.
Re^2: How to decide which implementation to use? by thor (Priest) on Feb 25, 2006 at 15:29 UTC
IMO, in some contexts, this could be construed as false laziness. Someone somewhere has to speak in these terms. To say that if you're talking about kernels and agents that your level of abstraction is too deep discounts this reality. thor `The only easy day was yesterday`	[reply]