HomeSort by relevance Sort by last modified time
    Searched full:consider (Results 126 - 150 of 2216) sorted by null

1 2 3 4 56 7 8 91011>>

  /external/chromium/crypto/
rsa_private_key_nss.cc 20 // TODO(rafaelw): Consider refactoring common functions and definitions from
109 // hardware-backed NSS DB. If it's not there, consider that an
  /external/chromium/third_party/libjingle/source/talk/base/
byteorder.h 45 // TODO: Consider NetworkEndian as synonym for BigEndian, for clarity in use.
46 // TODO: Consider creating optimized versions, such as direct read/writes of
httpcommon-inl.h 68 // TODO: Consider checking for invalid data following port number.
83 // TODO: consider failing in this case.
  /external/icu4c/common/unicode/
ucnvsel.h 64 * to consider only roundtrip mappings or also fallbacks.
132 * @param sel selector to consider
  /external/llvm/docs/HistoricalNotes/
2001-02-09-AdveComments.txt 7 o We should consider eliminating the type annotation in cases where it is
117 size should not matter. I think we should consider it because I find it
2000-11-18-EarlyDesignIdeasResp.txt 11 > architecture interface first (i.e., consider the code generation and
52 > 2. Design issues to consider (an initial list that we should continue
67 Here are some other auxiliary goals that I think we should consider:
  /external/webkit/Tools/Scripts/webkitpy/common/net/
testoutput_unittest.py 65 # FIXME: should consider using MockFileSystem here so as to not
74 # FIXME: should consider using MockFileSystem here so as to not
  /frameworks/base/core/java/android/net/
NetworkTemplate.java 189 // TODO: consider matching against WiMAX subscriber identity
219 // TODO: consider matching against WiMAX subscriber identity
  /frameworks/base/core/java/android/webkit/
DeviceOrientationService.java 149 // TODO: Consider handling multiple sensors.
159 // TODO: Consider handling multiple sensors.
  /frameworks/base/docs/html/guide/topics/testing/
what_to_test.jd 7 test. This document lists some most common Android-related situations that you should consider
27 re-start the foreground Activity. You should consider testing the following:
  /frameworks/base/docs/html/guide/topics/ui/notifiers/
index.jd 46 the user to respond and take action, consider using a
67 while your Activity is still in focus, consider using a
  /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/project/
AndroidManifestHelper.java 45 * {@link XmlErrorListener}. To use a different error handler, consider using
107 * {@link XmlErrorListener}. To use a different error handler, consider using
  /external/guava/src/com/google/common/primitives/
Booleans.java 76 * <p><b>Note:</b> consider representing the array as a {@link
99 * <p><b>Note:</b> consider representing the array as a {@link BitSet}
112 // TODO: consider making this public
166 // TODO: consider making this public
299 * <p><b>Note:</b> consider representing the collection as a {@link
  /external/pcre/doc/html/
pcrepartial.html 37 Consider, for example, an application where a human is required to type in data
123 the data that is returned. Consider this pattern:
199 different from <b>pcre_exec</b> when PCRE_PARTIAL_HARD is set. Consider the
212 results. Consider this pattern:
310 and $. Consider an unanchored pattern that matches dates:
357 longer possible. Consider again this <b>pcretest</b> example:
393 PCRE_DFA_RESTART is used with <b>pcre_dfa_exec()</b>. For example, consider this
  /external/pcre/doc/
pcrepartial.3 13 Consider, for example, an application where a human is required to type in data
94 the data that is returned. Consider this pattern:
169 different from \fBpcre_exec\fP when PCRE_PARTIAL_HARD is set. Consider the
184 results. Consider this pattern:
286 and $. Consider an unanchored pattern that matches dates:
331 longer possible. Consider again this \fBpcretest\fP example:
366 PCRE_DFA_RESTART is used with \fBpcre_dfa_exec()\fP. For example, consider this
  /external/clang/test/SemaCXX/
member-pointer.cpp 304 return (*((A**) 0)) // expected-warning {{indirection of non-volatile null pointer will be deleted}} expected-note {{consider}}
305 ->**(int A::**) 0; // expected-warning {{indirection of non-volatile null pointer will be deleted}} expected-note {{consider}}
312 .**(int A::**) 0; // expected-warning {{indirection of non-volatile null pointer will be deleted}} expected-note {{consider}}
  /external/proguard/src/proguard/
Initializer.java 242 System.out.println(" You should consider explicitly keeping the mentioned classes");
259 System.out.println(" You might consider explicitly keeping the mentioned classes and/or");
268 System.out.println(" You should consider explicitly keeping the mentioned class members");
  /external/webkit/Source/WebKit/chromium/src/
WebSearchableFormData.cpp 81 // FIXME: Consider refactoring this code so that we don't call form->associatedElements() twice.
161 // FIXME: Consider refactoring this code so that we don't call form->associatedElements() twice.
233 // Only consider forms that GET data and the action targets an http page.
  /bionic/libm/src/
k_sin.c 25 * 1. Since sin(-x) = -sin(x), we need only to consider positive x.
s_nan.c 68 * consider valid, so we might be violating the C standard. But it's
  /cts/tests/tests/content/src/android/content/pm/cts/
ApplicationInfoTest.java 61 // TODO: consider expanding to check all member variables
  /cts/tools/tradefed-host/src/com/android/cts/tradefed/result/
TestResultRepo.java 102 // TODO: consider caching the results in future
  /cts/tools/tradefed-host/src/com/android/cts/tradefed/testtype/
ResultFilter.java 137 // 'testEnded'. TODO: consider adding an explict API for reporting an unexecuted
  /development/samples/HoneycombGallery/src/com/example/android/hcgallery/
FitCenterFrameLayout.java 73 // Fit and center the child within the parent. Make sure not to consider padding
  /development/tools/emulator/opengl/tests/event_injector/
iolooper.h 65 * consider the scenario, when "server" does two sequential writes, and "client"

Completed in 676 milliseconds

1 2 3 4 56 7 8 91011>>