Searched
full:consider (Results
501 -
525 of
4787) sorted by null
<<21222324252627282930>>
/system/nativepower/client/ |
power_manager_client.cc | 136 // TODO: Try to get a new handle periodically; also consider notifying
|
/system/update_engine/ |
system_state.h | 62 // TODO(jaysri): Consider renaming this to something like GlobalContext.
|
/toolchain/binutils/binutils-2.25/config/ |
iconv.m4 | 39 am_cv_func_iconv="no, consider installing GNU libiconv"
|
/toolchain/binutils/binutils-2.25/include/opcode/ |
mn10200.h | 52 in the order in which the disassembler should consider
|
/toolchain/binutils/binutils-2.25/libiberty/ |
README | 45 * Consider the special cases of building libiberty; as of this
|
/developers/build/prebuilts/gradle/JumpingJack/Wearable/src/main/java/com/example/android/wearable/jumpingjack/ |
MainActivity.java | 65 * we consider that a successful count. 160 * GRAVITY_THRESHOLD. We also consider the up <-> down movement successful if it takes less than
|
/developers/samples/android/wearable/wear/JumpingJack/Wearable/src/main/java/com/example/android/wearable/jumpingjack/ |
MainActivity.java | 65 * we consider that a successful count. 160 * GRAVITY_THRESHOLD. We also consider the up <-> down movement successful if it takes less than
|
/development/samples/browseable/JumpingJack/src/com.example.android.wearable.jumpingjack/ |
MainActivity.java | 65 * we consider that a successful count. 160 * GRAVITY_THRESHOLD. We also consider the up <-> down movement successful if it takes less than
|
/external/chromium-trace/catapult/third_party/gsutil/gslib/addlhelp/ |
prod.py | 64 2. If your business depends on timely data transfer, you should consider 103 (say hundreds of thousands or more), you should consider tracking your
|
/external/clang/docs/analyzer/ |
nullability.rst | 9 Let's consider the following 2 categories: 63 A symbol may need to be treated differently inside an inlined body. For example, consider these conversions from nonnull to nullable in presence of inlining::
|
/external/elfutils/libdw/ |
fde.c | 161 /* We have a new FDE to consider. */ 306 /* We have a new FDE to consider. */
|
/external/guava/guava/src/com/google/common/escape/ |
ArrayBasedUnicodeEscaper.java | 44 * replacement mapping consider using {@link ArrayBasedEscaperMap}. 122 // any values in that range. To see why, consider the case where:
|
/external/guava/guava/src/com/google/common/primitives/ |
UnsignedLong.java | 65 * <p>To represent decimal constants less than {@code 2^63}, consider {@link #valueOf(long)} 71 // TODO(user): consider caching small values, like Long.valueOf
|
/external/jsilver/src/com/google/streamhtmlparser/impl/ |
ParserStateTable.java | 102 // TODO: Consider throwing run-time error here. 158 // TODO: Consider asserting if there was a state transition defined.
|
/external/llvm/docs/CommandGuide/ |
bugpoint.rst | 44 The "``--``" right after the **--args** option tells **bugpoint** to consider 59 consider any options starting with "``-``" to be part of the **--tool-args**
|
/external/llvm/lib/Target/AMDGPU/ |
SIFixSGPRLiveRanges.cpp | 135 // Only consider defs that are live outs. We don't care about def / 138 // LiveVariables does not consider registers that are only used in a
|
/external/opencv3/doc/py_tutorials/py_feature2d/py_fast/ |
py_fast.markdown | 28 3. Consider a circle of 16 pixels around the pixel under test. (See the image below) 78 2. Consider two adjacent keypoints and compute their \f$V\f$ values.
|
/external/opencv3/doc/py_tutorials/py_imgproc/py_filtering/ |
py_filtering.markdown | 127 function of space alone, that is, nearby pixels are considered while filtering. It doesn't consider 128 whether pixels have almost same intensity. It doesn't consider whether pixel is an edge pixel or
|
/external/opencv3/doc/py_tutorials/py_imgproc/py_histograms/py_2d_histogram/ |
py_2d_histogram.markdown | 15 intensity value of the pixel. But in two-dimensional histograms, you consider two features. Normally 86 Consider code:
|
/external/opencv3/doc/py_tutorials/py_imgproc/py_watershed/ |
py_watershed.markdown | 39 Consider the coins image below, the coins are touching each other. Even if you threshold it, it will 109 But we know that if background is marked with 0, watershed will consider it as unknown area. So we
|
/external/opencv3/doc/py_tutorials/py_photo/py_non_local_means/ |
py_non_local_means.markdown | 23 Consider a noisy pixel, \f$p = p_0 + n\f$ where \f$p_0\f$ is the true value of pixel and \f$n\f$ is the noise in 34 So idea is simple, we need a set of similar images to average out the noise. Consider a small window
|
/external/pcre/dist/doc/html/ |
pcrepartial.html | 37 Consider, for example, an application where a human is required to type in data 106 inspected while carrying out the match. For example, consider this pattern: 138 the data that is returned. Consider this pattern: 217 different from the standard functions when PCRE_PARTIAL_HARD is set. Consider 230 results. Consider this pattern: 335 \b, \B, and $. Consider an unanchored pattern that matches dates: 424 longer possible. Consider again this <b>pcretest</b> example: 460 used. For example, consider this pattern:
|
/external/proguard/src/proguard/ |
ConfigurationChecker.java | 115 System.out.println(" You should consider writing the output to a jar file, or otherwise"); 149 System.out.println(" members. You should specify at least some class members or consider");
|
/external/v8/src/arm64/ |
instructions-arm64.cc | 316 // xzr and Register are not defined in that header. Consider adding 328 // xzr and Register are not defined in that header. Consider adding
|
/frameworks/base/core/java/android/text/method/ |
TextKeyListener.java | 105 * @param cap the capitalization rules to consider. 196 // We consider special function keyboards full keyboards as a workaround for
|
Completed in 1834 milliseconds
<<21222324252627282930>>