| 4aa863a08a4fed2f8b8967f63e0df61d72f28b79 |
|
14-Oct-2010 |
Jesse Wilson <jessewilson@google.com> |
Fix Class.getMethods() for visibility bridge methods.
We had a bug where we couldn't find synthetic methods added by
subclasses to boost visibility of their superclass methods.
The old logic appeared to work fine with the covariant return
type synthetic methods, but broke down on these visibility
synthetic methods.
For reference, the general rules are:
- when there is a synthetic method for a covariant return type,
include it in getMethods() but prefer the natural method on
getMethod() calls.
- when there is a synthetic method for a visibility boost, prefer
it over the superclass method on getMethods() and getMethod()
calls.
Change-Id: Ied1f9fc9892d211647da87959746839f7e0e1140
http://b/2908173
|
| 7e27918cf43b2e095cd10540185ffed81b843fa2 |
|
14-Oct-2010 |
Jesse Wilson <jessewilson@google.com> |
Fix Class.getMethods() for visibility bridge methods.
We had a bug where we couldn't find synthetic methods added by
subclasses to boost visibility of their superclass methods.
The old logic appeared to work fine with the covariant return
type synthetic methods, but broke down on these visibility
synthetic methods.
For reference, the general rules are:
- when there is a synthetic method for a covariant return type,
include it in getMethods() but prefer the natural method on
getMethod() calls.
- when there is a synthetic method for a visibility boost, prefer
it over the superclass method on getMethods() and getMethod()
calls.
Change-Id: Ied1f9fc9892d211647da87959746839f7e0e1140
http://b/2908173
|
| 4557728efb66c455a52b7669a8eefef7a9e54854 |
|
11-Aug-2010 |
Jesse Wilson <jessewilson@google.com> |
Moving tests to be under the libcore.* package.
This is indended to make it easier to run on VMs that restrict the packages
from which application classes can be loaded. For example, on the RI you need
to use the bootclasspath to load these tests.
Change-Id: I52193f35c5fcca18b5a3e1d280505b1e29b388af
|