Lines Matching refs:code

12   more importantly to hide code intended to be implementation only, driven by
25 To download the code and any dependencies required for building, see [DOWNLOADING.md](DOWNLOADING.m…
43     metalava extracts metadata from source code to generate artifacts such as the
146   not just nullness annotations found in the source code and annotations merged
149   compiler treat errors in the user code as warnings instead of errors.)
153   of the source code). This means that the documentation tool itself does not
154   need to be able to figure out which parts of the source code is included in
169 * Consistent stubs: In doclava1, the code which iterated over the API and
177   extraction code in doclava1 missed, but accidentally included in the SDK
186   Some of these take advantage of looking at the source code which wasn't
276   just one example, the code which generated documentation for typedef constants
284   typedefs (@IntDef and @StringDef classes) in the source code. Prior to this
285   this was generated manually via the development/tools/extract code. This also
290   separate code (tools/base/misc/api-generator), invoked during the build. This
314     a model not just from parsing source code, but from reading older SDK
320     to parse older source code which may no longer be easy to parse.
322 (2) There's a lot of logic for deciding whether code found in the source tree
355             // code operating on the class here
364 which limits itself to visiting code elements that are part of the API.
460 typedef macro), but should also help Dokka -- and arguably the Kotlin code which