Lines Matching refs:be

33 meaning. If you need to add any comments that should not be interpreted by the
49 These map files can (and should) also be used as version scripts for building
53 file. Without this, APIs that you have not explicitly exposed will still be
55 symbol named in any `global:` group will be visible in the implementation
60 Version names that end with `_PRIVATE` or `_PLATFORM` will not be exposed in any
61 stubs, but will be exposed in the implementation library. Using either of these
68 interpreted by the stub generator. Multiple space-delimited tags may be used on
73 Indicates that the version or symbol is to be exposed by an APEX rather than the
76 May be used in combination with `llndk` if the symbol is exposed to both APEX
85 Warning: APIs marked `future` will be usable in any module with `sdk: "current"`
86 but **will not be included in the NDK**. `future` should generally not be used,
93 API level 21. This tag can be applied to either a version definition or an
102 **Symbol names for which no other rule applies will implicitly be introduced in
105 Code names can (and typically should) be used when defining new APIs. This
107 that release. For example, `introduced=S` can be used to define APIs added in S.
108 Any code name known to the build system can be used. For a list of versions
121 symbol is defined with only architecture-specific tags, it will not be present
124 Note: The architecture-specific tags should, in general, not be used. These are
131 Indicates that the version or symbol is to be exposed in the LL-NDK stubs rather
132 than the NDK. May be used in combination with `apex` if the symbol is exposed to
143 should not be exposed in the stub library. Developers can still access them via
144 `dlsym`, but they will not be exposed in the stubs so it should at least be
155 should be used for APIs exposed by an APEX to the platform or another APEX.
157 May be used in combination with `llndk` if the symbol is exposed to both APEX
160 Since a single library can be installed ether in platform or an apex, but not
165 practice". A #systemapi symbol can be dropped from the next release if we are
166 confident that no one is using it. Similarily, #apex can be dropped if we are
177 tag may be used.
207 Indicates that the symbol should be [weak] in the stub library.