Lines Matching refs:references

120 <p>The class references, field IDs, and method IDs are guaranteed valid until the class is unloaded…
158 <p>The only way to get non-local references is via the functions
172 <p>All JNI methods accept both local and global references as arguments.
173 It's possible for references to the same object to have different values.
176 <strong>To see if two references refer to the same object,
178 references with <code>==</code> in native code.</p>
181 <strong>must not assume object references are constant or unique</strong>
187 <p>Programmers are required to "not excessively allocate" local references.  In practical terms thi…
188 that if you're creating large numbers of local references, perhaps while running through an array of
192 16 local references, so if you need more than that you should either delete as you go or use
196 types, not object references, and should not be passed to
204 never automatically free local references until the thread detaches.  Any local
205 references you create will have to be deleted manually. In general, any native
206 code that creates local references in a loop probably needs to do some manual
228 are C-style pointers to primitive data rather than local references.  They
504 object references.</p>
543     <li><b>Weak global references</b>
544     <p>Until Android 2.2 (Froyo), weak global references were not implemented.
547     <p>Until Android 4.0 (Ice Cream Sandwich), weak global references could only
550     programmers to create hard references to weak globals before doing
552     <p>From Android 4.0 (Ice Cream Sandwich) on, weak global references can be
553     used like any other JNI references.</li>
554     <li><b>Local references</b>
555     <p>Until Android 4.0 (Ice Cream Sandwich), local references were
679     <code>JNI_OnLoad</code>, and cache the class references for later