Lines Matching refs:a

9 and each officially released API has a numbered file (e.g. "6.xml").
15 defined locally.  The tool can't easily tell anything about a dependency
16 beyond the name (e.g. whether a class is a static or non-static inner
28 analyze the APK, so if you have a large set of APKs it's best to run them
53     you disable both warnings and errors you will only see a summary.
78 This could be a Creator class in the package android.os.Parcelable,
82 The API XML does specify each package in a <package> tag, so we should have
84 at a time from the right until we match a known package.  This will work
95 If apkcheck sees a reference to an unknown field, and the field's defining
97 a warning instead of an error.
104 to verify that a method call on an annotation is valid.
106 If apkcheck sees a method call to an unknown method, and the class appears
108 fields or methods), we emit a warning instead of an error.
113 Suppose a class defines a method "public Foo gimmeFoo()".  Any subclass
115 there's no need to emit a method entry for gimmeFoo() in the subclasses.
119 is necessary to emit a new method entry, but the public API XML generator
122 If apkcheck can't find an exact match for a method reference, but can
123 find a method that matches on everything but the return type, it will
124 emit a warning instead of an error.  (We could be more thorough and try
140 a single letter, so apkcheck includes a kluge that converts single-letter
143 This often works, but falls apart in a few cases.  For example:
154 a method with a more specific return type (android.os.Parcelable), so
159 as a covariant return type.  When the generic type is in the parameter
164 may be worthwhile to try a little harder here.)
171 the app as a cookie.
177 If an APK refers to a non-public class, but doesn't access any fields
178 or methods, a warning is emitted instead of an error.