HomeSort by relevance Sort by last modified time
    Searched full:naming (Results 76 - 100 of 1241) sorted by null

1 2 34 5 6 7 8 91011>>

  /ndk/sources/cxx-stl/stlport/stlport/stl/
_iterator.h 165 //c is a Standard name (24.4.2.1), do no make it STLport naming convention compliant.
195 //c is a Standard name (24.4.2.3), do no make it STLport naming convention compliant.
224 //container is a Standard name (24.4.2.5), do no make it STLport naming convention compliant.
  /prebuilts/ndk/current/sources/cxx-stl/stlport/stlport/stl/
_iterator.h 165 //c is a Standard name (24.4.2.1), do no make it STLport naming convention compliant.
195 //c is a Standard name (24.4.2.3), do no make it STLport naming convention compliant.
224 //container is a Standard name (24.4.2.5), do no make it STLport naming convention compliant.
  /art/compiler/utils/arm64/
managed_register_arm64.cc 76 // FIXME: Find better naming.
  /external/antlr/antlr-3.4/antlr-ant/main/antlr3-task/
Readme.txt 30 Adapted the grammar type recognition to the changed naming conventions for tree parsers.
  /external/apache-harmony/support/src/test/resources/config/
excludes.xsd 21 * proper XML naming conventions (must begin with a
  /external/chromium-trace/catapult/third_party/gsutil/third_party/boto/boto/file/
README 8 because of the different naming semantics in these types of systems: the
  /external/chromium-trace/catapult/tracing/tracing/model/
object_snapshot.html 29 * e.g. recognizing domain-specific types and converting from C++ naming
  /external/curl/docs/libcurl/opts/
CURLOPT_CAINFO.3 31 Pass a char * to a zero terminated string naming a file holding one or more
CURLOPT_CRLFILE.3 31 Pass a char * to a zero terminated string naming a \fIfile\fP with the
CURLOPT_ISSUERCERT.3 31 Pass a char * to a zero terminated string naming a \fIfile\fP holding a CA
  /external/elfutils/
NOTES 69 Sections created in output files follow the naming of special section
  /external/libpcap/
README.sita 36 inter-device protocol and naming conventions are described in detail
  /external/libpng/contrib/conftest/
README 35 FILE NAMING
  /external/mockito/src/org/mockito/
MockSettings.java 64 * Specifies mock name. Naming mocks can be helpful for debugging - the name is used in all verification errors.
66 * Beware that naming mocks is not a solution for complex code which uses too many mocks or collaborators.
67 * <b>If you have too many mocks then refactor the code</b> so that it's easy to test/debug without necessity of naming mocks.
69 * <b>If you use &#064;Mock annotation then you've got naming mocks for free!</b> &#064;Mock uses field name as mock name. {@link Mock Read more.}
  /libcore/ojluni/src/main/java/java/io/
InvalidClassException.java 64 * @param cname a String naming the invalid class.
  /packages/inputmethods/LatinIME/native/jni/src/suggest/core/
suggest.h 26 // Naming convention
  /prebuilts/misc/common/swig/include/2.0.11/python/
pyname_compat.i 23 * the new naming convention. You can get the tool from the SWIG distribution:
  /prebuilts/misc/darwin-x86_64/sdl2/include/SDL2/
SDL_thread.h 126 * Thread naming is a little complicated: Most systems have very small
130 * UTF-8 (but using the naming limits of C identifiers is a better bet).
131 * There are no requirements for thread naming conventions, so long as the
135 * http://stackoverflow.com/questions/149932/naming-conventions-for-threads
  /prebuilts/misc/windows/sdl2/i686-w64-mingw32/include/SDL2/
SDL_thread.h 126 * Thread naming is a little complicated: Most systems have very small
130 * UTF-8 (but using the naming limits of C identifiers is a better bet).
131 * There are no requirements for thread naming conventions, so long as the
135 * http://stackoverflow.com/questions/149932/naming-conventions-for-threads
  /prebuilts/misc/windows/sdl2/include/
SDL_thread.h 126 * Thread naming is a little complicated: Most systems have very small
130 * UTF-8 (but using the naming limits of C identifiers is a better bet).
131 * There are no requirements for thread naming conventions, so long as the
135 * http://stackoverflow.com/questions/149932/naming-conventions-for-threads
  /prebuilts/misc/windows/sdl2/x86_64-w64-mingw32/include/SDL2/
SDL_thread.h 126 * Thread naming is a little complicated: Most systems have very small
130 * UTF-8 (but using the naming limits of C identifiers is a better bet).
131 * There are no requirements for thread naming conventions, so long as the
135 * http://stackoverflow.com/questions/149932/naming-conventions-for-threads
  /external/autotest/client/bin/
fsinfo_unittest.py 64 'naming: version': 2,
65 'naming: bsize': 4096,
  /external/chromium-trace/catapult/third_party/gsutil/gslib/addlhelp/
subdirs.py 41 rules, to try to make naming work the way users would expect. For example, in
89 require such marker objects to implement naming behavior consistent with
  /external/chromium-trace/catapult/third_party/gsutil/gslib/commands/
mv.py 142 # after successfully copying to its destination, and also causes naming
143 # behavior consistent with Unix mv naming behavior (see comments in
  /external/llvm/lib/IR/
ValueSymbolTable.cpp 64 // Otherwise, there is a naming conflict. Rename this value.
92 // Otherwise, there is a naming conflict. Rename this value.

Completed in 1529 milliseconds

1 2 34 5 6 7 8 91011>>