Nic Strong wrote: > I see your point. I am not a java expert but I am guessing there maybe > some conditions where the class loader my try to load the missing class > even though the code is not going to be called?
I don't know the granularity of the classloading. Certainly if you mix Android 2.0 APIs with older APIs, and just try using branching at that point, it'll fail. Isolating it into separate classes may work, though -- thought about that but didn't try it in my earlier multiple-version experiments. > But it is going to become > very unwieldy as we support more of the 2.0 apis (e.g > AccountManager/ContactsContract). Indubitably. I'll be looking at the new Contact APIs tomorrow, and I'll try to run some experiments with your proposed technique. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 1.0 In Print! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
