(sorry if this is obvious) if you have a hard reference to a class in another class, then the classloader will (try to) load that one too.
instead, use a factory to construct classes *by name* which implement an interface that describes the OS dependent stuff. this breaks the loader class chain and ensures that classes are only loaded by an OS which does in fact have them. At 1:43 PM +1300 11/18/09, Nic Strong wrote: >I think isolating the 2.0 calls to a separate class will work, but >in away this will become almost as unwieldy as the reflection method >(although I guessing will have some performance benefit over >reflection). >Please post what you find from your experiments. > >Thanks again, >Nic -- jason.vp.engineering.particle -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
