HomeSort by relevance Sort by last modified time
    Searched full:naming (Results 1 - 25 of 900) sorted by null

1 2 3 4 5 6 7 8 91011>>

  /external/dhcpcd/compat/
linkaddr.c 42 #define NAMING 0
59 int byte = 0, state = NAMING;
74 } else if (state == NAMING &&
82 case NAMING | DIGIT:
83 case NAMING | LETTER:
86 case NAMING | DELIM:
  /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.pde.api.tools.ee.j2se13_1.0.0.200901281111/org/eclipse/pde/api/tools/internal/api_stubs/
J2SE-1.3.zip 
  /external/guava/guava/src/com/google/common/base/
CaseFormat.java 30 * Hyphenated variable naming convention, e.g., "lower-hyphen".
35 * C++ variable naming convention, e.g., "lower_underscore".
40 * Java variable naming convention, e.g., "lowerCamel".
45 * Java and C++ class naming convention, e.g., "UpperCamel".
50 * Java and C++ constant naming convention, e.g., "UPPER_UNDERSCORE".
  /bionic/libc/bionic/
name_mem.c 45 * Returns -1 on error and sets errno. If it returns an error naming page
46 * aligned anonymous memory the kernel doesn't support naming, and an alternate
47 * method of naming memory should be used (like ashmem).
  /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.pde.api.tools.ee.j2se15_1.0.0.200901281111/org/eclipse/pde/api/tools/internal/api_stubs/
J2SE-1.5.zip 
  /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.pde.api.tools.ee.javase16_1.0.0.200901281111/org/eclipse/pde/api/tools/internal/api_stubs/
JavaSE-1.6.zip 
  /external/chromium_org/chrome/browser/performance_monitor/
constants.cc 20 // The prefix to the state of a profile's name, to prevent any possible naming
  /external/chromium_org/content/browser/download/
file_metadata_linux.h 20 // but it is used to keep the naming consistent.
  /external/chromium_org/content/common/
set_process_title_linux.h 14 // This signature and naming is to be compatible with most other Unix
  /external/clang/test/CXX/expr/expr.unary/expr.unary.op/
p3.cpp 6 // naming a pointer-to-member.
  /external/jpeg/
jconfig.manx 41 #define signal_catcher _abort /* hack for Aztec C naming requirements */
  /external/qemu/distrib/jpeg-6b/
jconfig.manx 41 #define signal_catcher _abort /* hack for Aztec C naming requirements */
  /hardware/libhardware/modules/
README.android 7 Modules are .so in /system/libs/hw/ and have a well defined naming
  /sdk/eclipse/plugins/com.android.ide.eclipse.tests/src/com/android/ide/eclipse/adt/internal/editors/layout/refactoring/testdata/
manifest-expected-completion17.txt 3 package : This attribute gives a unique name for the package, using a Java-style naming convention to avoid name collisions. For example, applications published by Google could have names of the form com.google.app.appname
  /external/chromium_org/third_party/tcmalloc/vendor/
TODO 14 shared libaries, and get rid of the profile-naming hack once we
38 shared libaries(), and get rid of the profile-naming hack once we
  /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.pde.api.tools.ee.j2se14_1.0.0.200901281111/org/eclipse/pde/api/tools/internal/api_stubs/
J2SE-1.4.zip 
  /external/clang/test/SemaObjC/
arc-decls.m 63 @synthesize newFoo; // expected-error {{property's synthesized getter follows Cocoa naming convention for returning}}
64 @synthesize copyBar; // expected-error {{property's synthesized getter follows Cocoa naming convention for returning}}
65 @synthesize allocBaz; // expected-error {{property's synthesized getter follows Cocoa naming convention for returning}}
  /external/llvm/test/CodeGen/R600/
README 12 - For all other tests, use your best judgement for organizing tests and naming
16 | Naming conventions |
  /frameworks/base/location/java/android/location/
IFusedGeofenceHardware.aidl 66 * Remarks: keep naming of geofence request options consistent with the naming used in
  /device/lge/hammerhead/overlay/frameworks/base/core/res/res/values-mcc440-mnc20/
config.xml 24 <!-- XXXXX NOTE THE FOLLOWING RESOURCES USE THE WRONG NAMING CONVENTION.
  /external/chromium_org/content/renderer/pepper/
gfx_conversion.h 16 // The style of naming is to match the PP_Bool conversions.
  /external/chromium_org/net/cert/
cert_database_android.cc 26 // CertInstaller activity, which handles verification, naming,
  /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/builderTemplate/componentScripts/
build.properties 45 # Type of build. Used in naming the build output. Typically this value is
51 # ID of the build. Used in naming the build output.
56 # Label for the build. Used in naming the build output
61 # Timestamp for the build. Used in naming the build output
  /ndk/tests/device/issue42891-boost-1_52/jni/boost/boost/test/utils/runtime/cla/
named_parameter.hpp 55 // Naming policy interface
  /prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.4.3/sysroot/usr/include/linux/
cm4000_cs.h 9 * used by existing userspace programs, so I kepth the awkward "bIFSD" naming

Completed in 2080 milliseconds

1 2 3 4 5 6 7 8 91011>>