Lines Matching refs:code

12   more importantly to hide code intended to be implementation only, driven by
40     metalava extracts metadata from source code to generate artifacts such as the
143   not just nullness annotations found in the source code and annotations merged
146   compiler treat errors in the user code as warnings instead of errors.)
150   of the source code). This means that the documentation tool itself does not
151   need to be able to figure out which parts of the source code is included in
166 * Consistent stubs: In doclava1, the code which iterated over the API and
174   extraction code in doclava1 missed, but accidentally included in the SDK
183   Some of these take advantage of looking at the source code which wasn't
273   just one example, the code which generated documentation for typedef constants
281   typedefs (@IntDef and @StringDef classes) in the source code. Prior to this
282   this was generated manually via the development/tools/extract code. This also
287   separate code (tools/base/misc/api-generator), invoked during the build. This
311     a model not just from parsing source code, but from reading older SDK
317     to parse older source code which may no longer be easy to parse.
319 (2) There's a lot of logic for deciding whether code found in the source tree
352             // code operating on the class here
361 which limits itself to visiting code elements that are part of the API.
457 typedef macro), but should also help Dokka -- and arguably the Kotlin code which