Probably true on Android, not universally true. Would fail on standard Java, like I said, if -Xfuture were specified.
On Oct 21, 5:27 pm, fadden <[email protected]> wrote: > On Oct 20, 11:10 am, DanH <[email protected]> wrote: > > > The wrapper class example is defective if the verifier is > > "conventional" -- doesn't have the swizzle you describe since 1.6. > > It works because the code does something like: > > if (version is 2.0 or later) > use wrapped stuff > else > feature not available, do nothing > > The wrapper class would fail verification and not be usable, but > references *to* the wrapped class would be okay. Verification happens > between loading and initialization. If class C refers to class D, the > VM needs to be able to load D and examine it, but does not need to > initialize and verify D in order to verify C. This is still true in > older versions of Android. -- 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
