Home	Sort by relevance Sort by last modified time

Full Search Definition Symbol File Path History   | | Help

    Searched full:separate (Results 1001 - 1025 of 6153) sorted by null

<<41424344454647484950>>

/cts/tools/dasm/src/java_cup/
lr_item_core.java	159 /** Equality comparison for the core only. This is separate out because we 160 * need separate access in a super class.
/development/samples/ApiDemos/src/com/example/android/apis/app/
ServiceStartArguments.java	114 // separate thread because the service normally runs in the process's 207 * all together; typically this code would appear in some separate class.
/development/samples/BackupRestore/src/com/example/android/backuprestore/
BackupRestoreActivity.java	74 * <li>{@link MultiRecordExampleAgent} - this agent stores each separate bit of data 75 * managed by the UI in separate records within the backup dataset. It illustrates
/development/samples/HoneycombGallery/src/com/example/android/hcgallery/
ContentFragment.java	316 // We perform the actual disk write operations on a separate thread using the 323 * Compress and write the bitmap to disk on a separate thread.
/external/apache-xml/src/main/java/org/apache/xalan/templates/
DecimalFormatProperties.java	370 * pattern-separator specifies the character used to separate positive 383 * pattern-separator specifies the character used to separate positive
/external/chromium/sdch/open-vcdiff/src/
encodetable.cc	34 // separate sections. This facilitates providing partially 223 // instead of separate sections for instructions, addresses, and data,
/external/chromium/sdch/open-vcdiff/src/gtest/
README	114 inside the source code tree, or in a separate directory. We recommend building 115 in a separate directory as that tends to produce both more consistent results
/external/chromium_org/chrome/browser/history/
thumbnail_database.h	27 // history thread. It is a totally separate component from history partially 31 // of the data). Moving this to a separate thread would not block potentially
/external/chromium_org/chrome/browser/profiles/
off_the_record_profile_io_data.cc	290 // Use a separate in-memory cookie store for the app. 295 // Use a separate in-memory cache for the app.
/external/chromium_org/chrome/
chrome_resources.gyp	16 # used by internal pages. Putting them in a separate pak file makes 440 # are copied into the installer. Note that we have a separate
/external/chromium_org/content/plugin/
plugin_channel.cc	223 // Separate vector::erase and ~WebPluginDelegateStub. 287 // Separate vector::erase and ~WebPluginDelegateStub.
/external/chromium_org/native_client_sdk/src/doc/devguide/coding/
application-structure.rst	31 more separate .js files; 33 separate .css files;
/external/chromium_org/net/url_request/
url_request_throttler_entry.cc	122 // the entry, otherwise separate clients could end up holding separate
/external/chromium_org/sdch/open-vcdiff/src/
encodetable.cc	51 // separate sections. This facilitates providing partially 255 // instead of separate sections for instructions, addresses, and data,
/external/chromium_org/third_party/angle/src/compiler/
SymbolTable.h	69 // There could be a separate class heirarchy for Constant variables; 72 // seem worth having separate classes, and "getConst" can't simply return
/external/chromium_org/third_party/icu/source/test/intltest/
idnaref.h	117 * into separate labels, decide whether to apply allowUnassigned and useSTD3ASCIIRules on each, 157 * into separate labels, decide whether to apply allowUnassigned and useSTD3ASCIIRules on each,
/external/chromium_org/third_party/libjingle/source/talk/session/media/
channelmanager.h	49 // ChannelManager allows the MediaEngine to run on a separate thread, and takes 53 // channels are stored in separate vectors, to easily allow operations on just
srtpfilter.h	194 // cipher-suite and key. Receiving must be done by a separate session. 197 // cipher-suite and key. Sending must be done by a separate session.
/external/chromium_org/third_party/protobuf/src/google/protobuf/compiler/
importer.h	61 // TODO(kenton): Move all SourceTree stuff to a separate file? 159 // separate Importer object to import each one (but use the same
/external/chromium_org/third_party/qcms/src/
transform-sse1.c	49 * locations in separate registers */ 169 * locations in separate registers */
transform-sse2.c	49 * locations in separate registers */ 163 * locations in separate registers */
/external/chromium_org/third_party/skia/src/gpu/
GrDefaultPathRenderer.cpp	59 // when we have separate stencil we increment front faces / decrement back faces 83 // When there are no separate faces we do two passes to setup the winding rule
/external/chromium_org/third_party/sqlite/src/src/
mutex_unix.c	218 ** separate processes cannot read different values from the same 261 ** separate processes cannot read different values from the same
/external/chromium_org/third_party/sqlite/src/tool/
mksqlite3c.tcl	52 ** This file is an amalgamation of many separate C source files from SQLite 68 ** separate file. This file contains only code for the core SQLite library.
/external/clang/docs/
Modules.rst	84 However, this module import behaves quite differently from the corresponding ``#include <stdio.h>``: when the compiler sees the module import above, it loads a binary representation of the ``std.io`` module and makes its API available to the application directly. Preprocessor definitions that precede the import declaration have no impact on the API provided by ``std.io``, because the module itself was compiled as a separate, standalone module. Additionally, any linker flags required to use the ``std.io`` module will automatically be provided when the module is imported [#]_ 107 To enable modules, pass the command-line flag ``-fmodules`` [#]_. This will make any modules-enabled software libraries available as modules as well as introducing any modules-specific syntax. Additional `command-line parameters`_ are described in a separate section later. 146 Module maps are specified as separate files (each named ``module.map``) alongside the headers they describe, which allows them to be added to existing software libraries without having to change the library headers themselves (in most cases [#]_). The actual `Module map language`_ is described in a later section. 251 Within a module map file, modules are referred to by a *module-id*, which uses periods to separate each part of a module's name:     [all...]

Completed in 727 milliseconds

<<41424344454647484950>>