HomeSort by relevance Sort by last modified time
    Searched full:strategy (Results 351 - 375 of 1010) sorted by null

<<11121314151617181920>>

  /prebuilts/python/darwin-x86/2.7.5/include/python2.7/
codecs.h 43 yet done. This is part of the lazy load strategy for the encodings
  /prebuilts/python/linux-x86/2.7.5/include/python2.7/
codecs.h 43 yet done. This is part of the lazy load strategy for the encodings
  /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/editors/formatting/
AndroidXmlFormattingStrategy.java 87 * This strategy is also used for delegation. If the user has chosen to use the
88 * standard Eclipse XML formatter, this strategy simply delegates to the
89 * default XML formatting strategy in WTP.
624 // this delegating strategy to supply the correct values when it is called
    [all...]
  /external/llvm/lib/CodeGen/
MachineTraceMetrics.cpp 80 // those instructions don't depend on any given trace strategy.
281 // A trace selection strategy is implemented as a sub-class of Ensemble. The
373 // Get an Ensemble sub-class for the requested trace strategy.
375 MachineTraceMetrics::getEnsemble(MachineTraceMetrics::Strategy strategy) {
376 assert(strategy < TS_NumStrategies && "Invalid trace strategy enum");
377 Ensemble *&E = Ensembles[strategy];
382 switch (strategy) {
384 default: llvm_unreachable("Invalid trace strategy enum")
    [all...]
  /external/aac/libAACdec/src/
rvlc.cpp 820 CHAR Strategy[60]="No";
    [all...]
  /external/apache-http/src/org/apache/http/impl/client/
AbstractHttpClient.java 95 /** The connection re-use strategy. */
98 /** The connection keep-alive strategy. */
DefaultRequestDirector.java 120 /** The connection re-use strategy. */
123 /** The keep-alive duration strategy. */
185 ("Connection reuse strategy may not be null.");
189 ("Connection keep alive strategy may not be null.");
    [all...]
  /external/apache-http/src/org/apache/http/impl/entity/
LaxContentLengthStrategy.java 46 * The lax implementation of the content length strategy.
48 * This strategy conforms to the entity transfer rules outlined in
  /external/ceres-solver/internal/ceres/
trust_region_minimizer_test.cc 243 scoped_ptr<TrustRegionStrategy> strategy(
245 minimizer_options.trust_region_strategy = strategy.get();
  /external/chromium/webkit/glue/media/
buffered_resource_loader.cc 462 void BufferedResourceLoader::UpdateDeferStrategy(DeferStrategy strategy) {
463 defer_strategy_ = strategy;
  /external/chromium_org/chrome/browser/extensions/api/declarative_webrequest/
webrequest_action.h 120 // strategy is STRATEGY_DEFAULT.
161 HostPermissionsStrategy strategy);
  /external/chromium_org/third_party/angle/include/GLSLANG/
ShaderLang.h 178 // compiler, selects the strategy for the clamping implementation.
259 // Selects a strategy to use when implementing array index clamping.
  /external/chromium_org/third_party/zlib/contrib/minizip/
zip.c 1059 int windowBits,int memLevel, int strategy,
    [all...]
  /external/chromium_org/tools/resources/
optimize-png-files.sh 247 # TODO(oshima): Experiment with strategy 1.
248 echo -n "|strategy"
  /external/clang/lib/CodeGen/
CGObjCRuntime.cpp 104 // We need to compute an access strategy for this bit-field. We are given the
106 // from the original layout. We reuse the normal bit-field access strategy by
  /external/guava/guava/src/com/google/common/eventbus/
EventBus.java 130 * Strategy for finding handler methods in registered objects. Currently,
205 * {@link HandlerFindingStrategy}; the default strategy is the
  /external/robolectric/src/test/java/com/xtremelabs/robolectric/shadows/
DefaultRequestDirectorTest.java 266 ConnectionKeepAliveStrategy strategy = shadowOf((DefaultRequestDirector) Robolectric.getSentHttpRequestInfo(0).getRequestDirector()).getConnectionKeepAliveStrategy(); local
267 assertSame(strategy, connectionKeepAliveStrategy);
  /external/zlib/src/contrib/ada/
zlib.ads 114 -- Compression strategy constants --
137 Strategy : in Strategy_Type := Default_Strategy;
  /external/zlib/src/contrib/minizip/
zip.c 1059 int windowBits,int memLevel, int strategy,
    [all...]
  /frameworks/base/docs/html/design/patterns/
widgets.jd 105 <p>Planning a resize strategy for your widget depends on the type of widget you're creating. List or grid-based collection widgets are usually straightforward because resizing the widget will simply expand or contract the vertical scrolling area. Regardless of the of the widget's size, the user can still scroll all information elements into view. Information widgets on the other hand require a bit more hands-on planning, since they are not scrollable and all content has to fit within a given size. You will have to dynamically adjust your widget's content and layout to the size the user defined through the resize operation.</p>
114 <li>In fact, as the user resizes a widget, the system will respond with a dp size range in which your widget can redraw itself. Planning your widget resizing strategy across "size buckets" rather than variable grid dimensions will give you the most reliable results.</li>
  /hardware/libhardware/include/hardware/
audio_policy.h 209 /* return the strategy corresponding to a given stream type */
224 uint32_t strategy,
  /art/compiler/sea_ir/types/
type_inference.cc 130 // TODO: Figure out strategy for two-register operands (double, long)
  /docs/source.android.com/src/source/
code-lines.jd 161 The source management strategy above includes a code-line that Google will keep private. The
  /external/apache-harmony/archive/src/test/java/org/apache/harmony/archive/tests/java/util/zip/
DeflaterTest.java 747 assertEquals("getTotalOut() for the default strategy did not correspond with JDK",
753 assertEquals("getTotalOut() for the Huffman strategy did not correspond with JDK",
758 assertEquals("Total Out for the Filtered strategy did not correspond with JDK",
784 "IllegalArgumentException not thrown when setting strategy to an invalid value.");
    [all...]
  /external/apache-http/src/org/apache/http/impl/
DefaultConnectionReuseStrategy.java 49 * Default implementation of a strategy deciding about connection re-use.

Completed in 911 milliseconds

<<11121314151617181920>>