Home	Sort by relevance Sort by last modified time

Full Search Definition Symbol File Path History   | | Help

    Searched full:consider (Results 276 - 300 of 4787) sorted by null

<<11121314151617181920>>

/external/icu/icu4c/source/common/unicode/
ucnvsel.h	67 * to consider only roundtrip mappings or also fallbacks. 135 * @param sel selector to consider
/external/ims/rcs/rcsmanager/src/java/com/android/ims/internal/
Logger.java	200 * Print the debug log and don't consider the traceLevel 210 * Print the debug log and don't consider the traceLevel
/external/llvm/docs/Frontend/
PerformanceTips.rst	70 types <t_aggregate>` (i.e. structs and arrays). As an alternative, consider 123 Other Things to Consider 135 source language, you may consider using fences instead. 161 #. In hot loops, consider duplicating instructions from small basic blocks 256 checks, type checks, range checks) consider adding an extra execution or 261 #. If you language uses range checks, consider using the IRCE pass. It is not 272 If you didn't find what you were looking for above, consider proposing an piece 278 You should also consider describing the problem you're facing on `llvm-dev
/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/llvm/include/llvm/Analysis/
CaptureTracking.h	27 /// be expensive, so consider caching the results. The boolean ReturnCaptures 39 /// instruction are considered. This routine can be expensive, so consider
/external/opencv3/doc/py_tutorials/py_photo/py_inpainting/
py_inpainting.markdown	19 bad marks with its neighbouring pixels so that it looks like the neigbourhood. Consider the image 28 Method"** by Alexandru Telea in 2004. It is based on Fast Marching Method. Consider a region in the
/external/pcre/dist/doc/
pcrepartial.3	13 Consider, for example, an application where a human is required to type in data 79 inspected while carrying out the match. For example, consider this pattern: 108 the data that is returned. Consider this pattern: 186 different from the standard functions when PCRE_PARTIAL_HARD is set. Consider 201 results. Consider this pattern: 309 \eb, \eB, and $. Consider an unanchored pattern that matches dates: 392 longer possible. Consider again this \fBpcretest\fP example: 427 used. For example, consider this pattern:
/external/skia/src/image/
SkSurface.cpp	113 // Our content isn't held by any image now, so we can consider that content mutable. 114 // Raster surfaces need to be told it's safe to consider its pixels mutable again.
/external/squashfs-tools/RELEASE-READMEs/
README-2.1	81 If you find Squashfs useful then please consider making a donation, 82 particularly if you use Squashfs in a commercial product. Please consider
/external/webrtc/webrtc/base/
optionsfile.cc	33 // We do not consider this an error because we expect there to be no file 47 // We do not consider this an error. Instead we ignore the line and
/frameworks/base/core/jni/android/graphics/
CreateJavaOutputStreamAdaptor.cpp	82 // Consider the stream to be at the end, since there was an error. 98 // The error was not with the stream itself, but consider it to be at the
/frameworks/base/docs/html/design/wear/
watchfaces.jd	20 ambient modes, and consider how system user interface elements will interact with your design.</p> 42 <p>Glanceability is the single most important principle to consider when creating a watch face 51 <p>Android Wear devices come in different shapes and sizes. You will need to consider both 90 dial with hour and minute hands. In this case, consider the corner areas that are exposed 137 of screen available on the device. Consider the best design for your watch faces on all 166 <p>When designing for OLED screens, you should consider power efficiency and the screen 209 When designing a watch face, consider how the indicator will fall over the watch face.</p> 262 and fitness data. Consider the inclusion of data integration creatively. Avoid simply
/frameworks/base/docs/html/distribute/users/
know-your-user.jd	75 Consider using a survey to gather information about your users and their 78 question is something of an art. Also consider providing an appropriate
/frameworks/base/docs/html/training/design-navigation/
screen-planning.jd	27 <p>Let's consider an example application that allows users to browse through a set of categorized news stories and photos. One possible model for such an app is shown below in the form of an ERD.</p> 38 <p>Once you define the information model, you can begin to define the contexts necessary to enable users to effectively discover, view, and act upon the data in your application. In practice, one way to do this is to <em>determine the exhaustive set of screens</em> needed to allow users to navigate to and interact with the data. The set of screens we actually expose should generally vary depending on the target device; it's important to consider this early in the design process to ensure that the application can adapt to its environment.</p>
/packages/inputmethods/LatinIME/java/src/com/android/inputmethod/latin/utils/
TextRange.java	61 // spans that end at `start' or begin at `end'. Consider the following case: 71 // does not touch the word, so we don't need to consider it. That's why requesting
/system/core/base/
utf8.cpp	49 // TODO: Consider using std::wstring_convert once libcxx is supported on 105 // TODO: Consider using std::wstring_convert once libcxx is supported on
/external/guava/guava/src/com/google/common/primitives/
Booleans.java	84 * <p><b>Note:</b> consider representing the array as a {@link 107 * <p><b>Note:</b> consider representing the array as a {@link BitSet} 120 // TODO(kevinb): consider making this public 174 // TODO(kevinb): consider making this public 308 * <p><b>Note:</b> consider representing the collection as a {@link
/external/skia/src/gpu/
GrTextureParamsAdjuster.cpp	197 * rectangles to consider: 204 * We want to avoid using a domain if possible. We consider the above rectangles, the filter type, 206 * latter is true we only need to consider whether the filter would extend beyond the rects. 312 // don't consider it when computing the domain. 410 // TODO: Copy the texture and adjust the texture matrix (both parts need to consider
/frameworks/base/docs/html/distribute/tools/
localization-checklist.jd	105 Consider the vocabulary expansion, script requirements, character spacing and 156 used, you should consider implementing support for RTL layouts and text 307 Consider providing context information that may include: 483 Additionally, consider translating your apps? store listing details 805 testers to provide you with feedback: consider creating a <a href= 820 For highest visibility across countries, consider an international marketing 895 specific languages or countries, consider options for improving your 915 predictable. If your apps gets very popular in a language, consider 923 Consider setting up language-specific user groups, Google+ communities,
/cts/tools/tradefed-host/tests/src/com/android/cts/tradefed/result/
CtsXmlResultReporterTest.java	152 // TODO: consider doing xml based compare 188 // TODO: consider doing xml based compare 242 // TODO: consider doing xml based compare
/external/clang/test/SemaCXX/
member-pointer.cpp	315 return (*((A**) 0)) // expected-warning {{indirection of non-volatile null pointer will be deleted}} expected-note {{consider}} 316 ->**(int A::**) 0; // expected-warning {{indirection of non-volatile null pointer will be deleted}} expected-note {{consider}} 323 .**(int A::**) 0; // expected-warning {{indirection of non-volatile null pointer will be deleted}} expected-note {{consider}}
/frameworks/base/core/java/com/android/internal/content/
PackageMonitor.java	309 // We consider something to have changed regardless of whether 347 // We only consider something to have changed if this is 348 // not a replace; for a replace, we just need to consider
/frameworks/base/docs/html/design/get-started/
principles.jd	11 Consider these principles as you apply your own 57 sensible, beautiful defaults, but also consider fun, optional customizations that don't hinder 107 <p>Consider using pictures to explain ideas. They get people's attention and can be much more efficient
/frameworks/base/docs/html/training/articles/
security-tips.jd	83 app processes, instead consider using a 210 be confusing for users. For example, consider using the <a 235 <p>If you must create a new permission, consider whether you can accomplish 245 that you need to consider: 372 Consider if there is a way that your application logic can be 385 <p>You should also consider whether your application might be inadvertently 394 the client. Consider running any code using sensitive data on the client to 466 render content from the open web, consider providing your own renderer so 511 tunnel, consider using {@link javax.net.ssl.HttpsURLConnection} or 593 sensitive, you should consider applying a permission to make sure tha     [all...]

Completed in 870 milliseconds

<<11121314151617181920>>