| /external/quake/quake/src/WinQuake/data/ |
| MANUAL.TXT | 59 device. Once we perfect these, we'll be able to use them to transport
185 To pick up items, weapons, and power-ups, walk over them. If you can't
356 solely-designed for deathmatch play. Try them, you'll like them.
360 them by typing connect <server>.
531 are always important, and you do not want to ignore them!
656 your grievances on them anyway. Good hunting.
745 == if you activate the traps, the monsters can get caught by them. ==
[all...] |
| /external/v8/src/ |
| mark-compact.cc | 209 // reachable from the objects on the marking stack, but no longer push them on
210 // the marking stack. Instead, we mark them as both marked and overflowed.
214 // the heap looking for objects marked as overflowed, push them on the stack,
361 // Mark the map pointer and body, and push them on the marking stack.
543 // etc., and all objects reachable from them.
549 // There may be overflowed objects in the heap. Visit them now.
616 // push them on the marking stack. Stop early if the marking stack fills
705 // First we identify nonlive weak handles and mark them as pending
791 // back pointers, reversing them all at once. This allows us to find
813 // Follow back pointers, setting them to prototype
[all...] |
| scopeinfo.cc | 46 // Consider sorting them according to type as well?
67 // increasing order, so we can simply add them to the
69 // not true for context-allocated locals: Some of them
75 // sort them by context slot index before adding them to the
|
| /external/webkit/ |
| NOTICE | 89 complete object files to the recipients so that they can relink them
91 it. And you must show them these terms so they know their rights.
138 libraries that are incorporated in them. (We have not seen how to achieve
233 sections when you distribute them as separate works. But when you
323 copyright notice for the Library among them, as well as a reference
363 use both them and the Library together in an executable that you
506 safest to attach them to the start of each source file to most effectively
583 complete object files to the recipients, so that they can relink them
585 it. And you must show them these terms so they know their rights.
[all...] |
| /development/pdk/docs/source/ |
| code-style.jd | 15 : Never catch and ignore them without explanation.
21 : generally don't use them.
45 <li>Fields: should either be at the top of the file, or immediately before the methods that use them
122 <p>There are rare exceptions to this rule: certain test code and top-level code where you want to catch all kinds of errors (to prevent them from showing up in a UI, or to keep a batch job running). In that case you may catch generic Exception (or Throwable) and handle the error appropriately. You should think very carefully before doing this, though, and put in comments explaining why it is safe in this place.
222 The use and location of static imports have been mildly controversial issues. Some people would prefer static imports to be interspersed with the remaining imports, some would prefer them reside above or below all other imports. Additinally, we have not yet come up with a way to make all IDEs use the same ordering.
251 <p>Braces do not go on their own line; they go on the same line as the code before them. So:
268 <p>Exception: import lines can go over the limit because humans rarely see them. This also simplifies tool writing.
352 <p>Our parting thought: BE CONSISTENT. If you're editing code, take a few minutes to look at the code around you and determine its style. If they use spaces around their if clauses, you should too. If their comments have little boxes of stars around them, make your comments have little boxes of stars around them too.
|
| /dalvik/docs/ |
| dexopt.html | 38 compressed archive and stores them on the heap. This implies a separate
110 use 640 permissions to prevent other user applications from examining them.
112 other applications, but you cannot create, modify, or remove them.
148 the VM and run through them. Anything that fails to load is simply not
169 illegal instruction sequences so that we don't have to check for them at
|
| /development/pdk/docs/porting/ |
| build_cookbook.jd | 124 by the <code>include $(CLEAR_VARS)</code> line, so you can rely on them
224 them here. For example:</p>
266 them here. For example:</p>
502 them with the directory name:</p>
538 the linker to remove dead code from them. This is mostly useful if you want to add a static library
|
| /external/e2fsprogs/lib/et/ |
| com_err.texinfo | 154 supplied at all, and the programmer must supply them at any point at which
195 values between them can reliably pass error codes without loss of meaning;
387 place any form of interpretation on them, including ignoring them. For
535 customers, who persuaded them not to do so, for a while; Ted Anderson of
|
| /external/freetype/include/freetype/config/ |
| ftoption.h | 94 /* them to display normal gray-level anti-aliased glyphs. */
222 /* FT_EXPORT_DEF here if you want. If you leave them undefined, they */
227 /* them for certain configurations only. */
360 /* them for certain configurations only. */
[all...] |
| /external/iproute2/doc/ |
| ip-tunnels.tex | 72 Well, if you like such tricks, nobody may prohibit you to use them.
432 applies to them. The simplest (and the most useful in practice)
442 implemented in software and true queue management is impossible for them
444 on real physical interfaces and to map tunneled packets to them.
456 with some classifier and map them to class \verb|1:ABC|. F.e.\
|
| /frameworks/base/core/java/android/pim/vcard/ |
| VCardParser_V21.java | 303 // some data may have them, so we allow it.
605 * but today's vCard often contains other charset, so we allow them.
782 * For now, we exclude them.
809 // Apparently invalid line seen in Windows Mobile 6.5. Ignore them.
835 // this class allowed them, so keep it as is.
[all...] |
| /frameworks/base/docs/html/guide/topics/security/ |
| security.jd | 81 have them assigned the same user ID. By doing this, for purposes of security
160 <p>To enforce your own permissions, you must first declare them in your
219 user will see them:</p>
292 additional security facility available to them called
359 also need to hand specific URIs to other applications for them to operate on.
|
| /frameworks/base/docs/html/resources/articles/ |
| contacts.jd | 8 them to users as a single entity. This article describes how to use the new API
98 the user, the system locates such overlapping contacts and combines them into a
121 <li>One of them has a common short name for the other (for example,
123 <li>One of them has just a first or last name and it matches the other
387 old API and another using the new API. Let's plug them in. Add this code to
|
| /ndk/docs/ |
| CHANGES.TXT | 32 Previous behaviour was to silently ignore them.
148 them. This is primarily to ease development. All you need to do is put a patch
220 and will even refuse to build some of them.
311 at android.git.kernel.org and nicely package them into a tarball that can
378 how to make a simple Android application that uses them.
|
| /prebuilt/darwin-x86/toolchain/arm-eabi-4.2.1/man/man1/ |
| arm-eabi-ar.1 | 186 any of the following, but you must specify only one of them:
205 you can use the \fBa\fR, \fBb\fR, or \fBi\fR modifiers to move them to a
263 first instance; to see them all, you must ask for a complete
300 names when putting them in the archive.
317 Preserve the \fIoriginal\fR dates of members when extracting them. If
|
| /prebuilt/darwin-x86/toolchain/arm-eabi-4.3.1/man/man1/ |
| arm-eabi-ar.1 | 197 any of the following, but you must specify only one of them:
216 you can use the \fBa\fR, \fBb\fR, or \fBi\fR modifiers to move them to a
274 first instance; to see them all, you must ask for a complete
313 names when putting them in the archive.
330 Preserve the \fIoriginal\fR dates of members when extracting them. If
|
| /prebuilt/darwin-x86/toolchain/arm-eabi-4.4.0/man/man1/ |
| arm-eabi-ar.1 | 197 any of the following, but you must specify only one of them:
216 you can use the \fBa\fR, \fBb\fR, or \fBi\fR modifiers to move them to a
274 first instance; to see them all, you must ask for a complete
313 names when putting them in the archive.
330 Preserve the \fIoriginal\fR dates of members when extracting them. If
|
| /prebuilt/linux-x86/toolchain/arm-eabi-4.2.1/man/man1/ |
| arm-eabi-ar.1 | 186 any of the following, but you must specify only one of them:
205 you can use the \fBa\fR, \fBb\fR, or \fBi\fR modifiers to move them to a
263 first instance; to see them all, you must ask for a complete
300 names when putting them in the archive.
317 Preserve the \fIoriginal\fR dates of members when extracting them. If
|
| /prebuilt/linux-x86/toolchain/arm-eabi-4.3.1/man/man1/ |
| arm-eabi-ar.1 | 197 any of the following, but you must specify only one of them:
216 you can use the \fBa\fR, \fBb\fR, or \fBi\fR modifiers to move them to a
274 first instance; to see them all, you must ask for a complete
313 names when putting them in the archive.
330 Preserve the \fIoriginal\fR dates of members when extracting them. If
|
| /prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/man/man1/ |
| arm-eabi-ar.1 | 197 any of the following, but you must specify only one of them:
216 you can use the \fBa\fR, \fBb\fR, or \fBi\fR modifiers to move them to a
274 first instance; to see them all, you must ask for a complete
313 names when putting them in the archive.
330 Preserve the \fIoriginal\fR dates of members when extracting them. If
|
| /prebuilt/linux-x86/toolchain/i686-unknown-linux-gnu-4.2.1/man/man1/ |
| i686-unknown-linux-gnu-ar.1 | 186 any of the following, but you must specify only one of them:
205 you can use the \fBa\fR, \fBb\fR, or \fBi\fR modifiers to move them to a
263 first instance; to see them all, you must ask for a complete
300 names when putting them in the archive.
317 Preserve the \fIoriginal\fR dates of members when extracting them. If
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/editors/manifest/descriptors/ |
| AndroidManifestDescriptors.java | 160 * It first computes the new children of the descriptor and then updates them
211 // These elements are referenced by already opened editors, so we want to update them
212 // but not re-create them when reloading an SDK on the fly.
346 * It then finds all children of the descriptor, inflate them recursively and set them
|
| /external/libpng/ |
| libpng.3 | [all...] |
| /bionic/libc/include/ |
| stdio.h | 175 * The following three definitions are for ANSI C, which took them
177 * made them official arguments to setvbuf(), without renaming them.
|
| /bionic/libc/kernel/ |
| README.TXT | 174 using them anyway.
257 what we do is keep a set of "original" kernel headers, and process them
265 source tree, we want to keep them at the same location in our generated
|
