| /external/chromium-trace/catapult/third_party/gsutil/third_party/boto/boto/logs/ |
| layer1.py | 119 You must use the following guidelines when naming a log group:
148 You must use the following guidelines when naming a log
|
| /external/clang/www/analyzer/ |
| release_notes.html | 266 <li>The analyzer is now far more aggressive with checking conformance with Core Foundation conventions. Any function that returns a CF type must now obey the Core Foundation naming conventions, or use the <a href="/annotations.html#attr_cf_returns_retained">cf_returns_retained</a> or <a href="/annotations.html#attr_cf_returns_not_retained">cf_returns_not_retained</a> annotations.</li>
341 <li>Introduces new attribute <a href="annotations.html#attr_ns_consumes_self">ns_consumes_self</a> to educate the Objective-C retain/release checker about custom "init-like" methods that do not follow the standard Cocoa naming conventions.</li>
|
| /external/deqp/framework/delibs/coding_guidelines/ |
| de-coding-guidelines.html | 433 <li><span class="heading">Naming conventions and formatting</span>
435 <li><span class="heading">Basic naming conventions</span>
440 <p>Anything which has a reasonable possibility of causing a naming conflict should be
479 <p>Naming your variables is somewhat of a black art, but the main goal of giving a name should
487 Thus one often successful approach for variable naming is to give name for the value instead.
491 <p>Consistency is one important factor in naming variables. When a similar kind of name is needed
[all...] |
| /external/iproute2/man/man8/ |
| tc.8 | 393 .SH NAMING
424 parent classes, only to their parent qdisc. The same naming custom as for
|
| /external/libxml2/include/libxml/ |
| tree.h | 634 * Macro for compatibility naming layer with libxml1. Maps
644 * Macro for compatibility naming layer with libxml1. Maps
[all...] |
| /external/slf4j/log4j-over-slf4j/compatibility/lib/ |
| logback-core-0.9.8-SNAPSHOT.jar | |
| log4j-1.3alpha-8.jar | |
| /external/v8/test/cctest/ |
| cctest.h | 593 // Prefixing the below with main_ reduces a lot of naming clashes.
606 // Prefixing the below with main_ reduces a lot of naming clashes.
|
| /frameworks/rs/api/ |
| rs_value_types.spec | 39 Entries of a vector can be accessed using different naming styles.
60 repeated, as long as we're not trying to assign to it. You also can't mix the naming
|
| /libcore/ojluni/src/main/java/java/sql/ |
| package.html | 267 Java Naming and Directory Interface<sup><font size=-2>TM</font></sup>
269 naming service and also for retrieving it.
|
| /libcore/ojluni/src/main/java/java/util/ |
| ServiceLoader.java | 80 * once, then the duplicates are ignored. The configuration file naming a
280 // The URL naming the configuration file to be parsed
|
| /libcore/ojluni/src/main/java/java/util/logging/ |
| FileHandler.java | 305 * @param pattern the pattern for naming the output file
342 * @param pattern the pattern for naming the output file
|
| /libcore/ojluni/src/main/java/javax/sql/rowset/spi/ |
| package.html | 48 the naming convention to be used.)
287 Furthermore, the <code>SyncProvider</code> naming convention <b>must</b> be followed as
|
| /libcore/ojluni/src/main/java/sun/security/x509/ |
| X400Address.java | 388 * <li>NAME_NARROWS = 1: input name narrows name (is lower in the naming subtree)
389 * <li>NAME_WIDENS = 2: input name widens name (is higher in the naming subtree)
|
| /prebuilts/go/darwin-x86/doc/ |
| debugging_with_gdb.html | 235 <h3 id="Naming">Naming</h3>
|
| /prebuilts/go/linux-x86/doc/ |
| debugging_with_gdb.html | 235 <h3 id="Naming">Naming</h3>
|
| /frameworks/base/core/java/android/content/ |
| Context.java | [all...] |
| /external/libhevc/common/arm/ |
| ihevc_intra_pred_filters_neon_intr.c | 470 /* Naming has been made as per the functionlity it has, For eg. pu1_src_tmp_1 is denoting pu1_src + 1 */
[all...] |
| /external/avahi/specs/ |
| draft-cheshire-dnsext-dns-sd-02.txt | 36 This document describes a convention for naming and structuring DNS
86 9. Flagship Naming................................................10
125 This document describes a convention for naming and structuring DNS
270 This document borrows the logical service naming syntax and semantics
321 wish, to continue naming their services using only letters, digits
[all...] |
| draft-cheshire-dnsext-dns-sd-03.txt | 36 This document describes a convention for naming and structuring DNS
87 9. Flagship Naming................................................20
125 This document describes a convention for naming and structuring DNS
270 This document borrows the logical service naming syntax and semantics
321 wish, to continue naming their services using only letters, digits
[all...] |
| /external/chromium-trace/catapult/third_party/gsutil/gslib/ |
| copy_helper.py | 439 Note that we don't disallow naming a bucket "sub-directory" where there's
500 Uses context-dependent naming rules that mimic Linux cp and mv behavior.
563 # Making naming behavior match how things work with local Linux cp and mv
574 # would (if using cp naming behavior) end up with paths like:
576 # whereas mv naming behavior should result in:
601 # Case 1. Handle naming rules for bucket subdir mv. Here we want to
[all...] |
| /external/chromium-trace/catapult/third_party/mapreduce/mapreduce/ |
| output_writers.py | 570 raise errors.BadWriterParamsError("Naming template is bad, %s" % (error))
572 raise errors.BadWriterParamsError("Naming template '%s' has extra "
609 # Validate the naming format does not throw any errors using dummy values
[all...] |
| /external/google-breakpad/src/client/mac/handler/ |
| minidump_generator.cc | [all...] |
| /frameworks/base/docs/html/guide/topics/security/ |
| permissions.jd | 570 avoid naming collisions, we recommend using reverse-domain-style naming for custom
682 component, naming the permission that controls access to
[all...] |
| /art/compiler/utils/arm/ |
| constants_arm.h | 271 // The naming of these accessor corresponds to figure A3-1.
|
