Re: Instances changing their type [was:Discover data patternso
Michael Kay wrote: > Of course all problems in computing can be solved by adding a layer of > indirection. You can design a wrapper object that implements the interface > and delegates all the work to either an ArrayList or a LinkedList. This > wrapper object is the only object to know about the implementation object so > only one place has to change when the implementation changes. But it would > be nice if this were built into the language, not something you have to > program yourself. Apart from anything else, forwarding all the method > invocations is expensive. Just for the discussion (I've seen Saxon's code ;-), a more efficient method would be to only use the List interface and eliminate all implementation class references, including initial creation, using a "dynamic" Factory. That Factrory could offer, besides some initial configuration via property file or whatnot, a runtime method to change the implementation at runtime through a console etc. Cheers, Manos
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format