Searched
full:them (Results
2076 -
2100 of
5167) sorted by null
<<81828384858687888990>>
/dalvik/dx/src/com/android/dx/dex/code/ |
OutputFinisher.java | 283 * Assigns indices in all instructions that need them, using the 378 * them. It also updates the given {@code formats} array so 654 * rewrites them to use a {@code goto} of some sort. In the
|
/dalvik/libcore/xml/src/main/java/org/apache/xml/dtm/ref/ |
IncrementalSAXSource_Filter.java | 349 // but we may want to pass them through when they exist... 353 // pause after them. As such, it may make more sense for folks who 354 // actually want to use them to register directly with the filter.
|
/dalvik/libcore/xml/src/main/java/org/w3c/dom/ |
Element.java | 17 * document. Elements may have attributes associated with them; since the 128 * explicitly clone <code>Attr</code> nodes to re-use them in other 298 * explicitly clone <code>Attr</code> nodes to re-use them in other
|
/dalvik/vm/ |
Globals.h | 388 * MUTEX ORDERING: when locking multiple mutexes, always grab them in 399 * we can use them in "thin locks". 459 /* Monitor list, so we can free them */
|
/development/docs/ |
howto_use_cupcake_sdk.txt | 107 If you have pre-0.9 projects in your Eclipse workspace, or if you import them 123 AIDL Java files are still present in the "src" folder. If yes, remove them. 350 could create a "client" AVD and a "server" AVD then run them both at once. The
|
/development/samples/ApiDemos/src/com/example/android/apis/view/ |
_package.html | 183 to be, so the LinearLayout just stacks them from top to bottom. 304 <p>Note that since view3 depends on the positions of both view1 and view2, it is defined after them in the layout 360 They simply arrange their children within whatever space is made available to them.
|
/external/bison/ |
COPYING | 36 source code. And you must show them these terms so they know their 120 sections when you distribute them as separate works. But when you 294 to attach them to the start of each source file to most effectively
|
/external/bison/doc/ |
fdl.texi | 67 them. 182 them a chance to provide you with an updated version of the Document. 307 list them all as Invariant Sections of your combined work in its
|
gpl.texi | 42 source code. And you must show them these terms so they know their 137 sections when you distribute them as separate works. But when you 335 to attach them to the start of each source file to most effectively
|
/external/blktrace/ |
COPYING | 36 source code. And you must show them these terms so they know their 120 sections when you distribute them as separate works. But when you 294 to attach them to the start of each source file to most effectively
|
LICENSE | 36 source code. And you must show them these terms so they know their 120 sections when you distribute them as separate works. But when you 294 to attach them to the start of each source file to most effectively
|
/external/bluetooth/bluez/ |
COPYING | 36 source code. And you must show them these terms so they know their 118 sections when you distribute them as separate works. But when you 289 to attach them to the start of each source file to most effectively
|
/external/bluetooth/glib/docs/reference/glib/ |
building.sgml | 265 putting them in a free list. However, memory profiling and debugging tools like <ulink 511 building them on your machine. 523 they are, then it will use them to rebuild the included
|
/external/bluetooth/hcidump/ |
COPYING | 36 source code. And you must show them these terms so they know their 120 sections when you distribute them as separate works. But when you 294 to attach them to the start of each source file to most effectively
|
/external/bzip2/ |
bzip2.1 | 142 in that order, and will process them 203 Check integrity of the specified file(s), but don't decompress them. 421 64-bit ints on some platforms which support them (GNU supported
|
bzip2.1.preformatted | 90 _B_Z_I_P_2 and _B_Z_I_P_, in that order, and will process them 137 decompress them. This really performs a trial 364 platforms which support them (GNU supported targets, and
|
bzip2.txt | 87 BZIP2 and BZIP, in that order, and will process them 134 decompress them. This really performs a trial 361 platforms which support them (GNU supported targets, and
|
/external/clearsilver/util/regex/ |
regex.h | 146 don't delete them!) */ 312 comparing them, or zero for no translation. The translation 460 /* Set REGS to hold NUM_REGS registers, storing them in STARTS and
|
/external/dbus/bus/ |
policy.c | 611 /* Now append them */ 970 * to them have a destination service name. [all...] |
/external/dnsmasq/ |
COPYING | 36 source code. And you must show them these terms so they know their 120 sections when you distribute them as separate works. But when you 294 to attach them to the start of each source file to most effectively
|
NOTICE | 36 source code. And you must show them these terms so they know their 120 sections when you distribute them as separate works. But when you 294 to attach them to the start of each source file to most effectively
|
/external/e2fsprogs/e2fsck/ |
pass1b.c | 10 * them. 450 * get the list of inodes, and merge them together. 760 * them to point to the new EA block.
|
/external/e2fsprogs/ext2ed/ |
COPYRIGHT | 43 source code. And you must show them these terms so they know their 127 sections when you distribute them as separate works. But when you 301 to attach them to the start of each source file to most effectively
|
/external/elfcopy/ |
NOTICE | 36 source code. And you must show them these terms so they know their 120 sections when you distribute them as separate works. But when you 294 to attach them to the start of each source file to most effectively
|
/external/elfutils/ |
COPYING.GPL | 36 source code. And you must show them these terms so they know their 120 sections when you distribute them as separate works. But when you 294 to attach them to the start of each source file to most effectively
|
Completed in 314 milliseconds
<<81828384858687888990>>