| /dalvik/libcore/xml/src/main/java/org/apache/xml/dtm/ref/ |
| ChunkedIntArray.java | 139 // We have to look all the way up the ancestor chain
|
| ExpandedNameTable.java | 197 // Look up the expanded name in the hash table. Return the id if
|
| /dalvik/vm/alloc/ |
| HeapBitmap.c | 268 /* The next index to look at.
|
| /dalvik/vm/interp/ |
| Stack.h | 91 stack might look like an uninterrupted series of interpreted method calls.
|
| /development/build/tools/ |
| make_windows_sdk.sh | 69 # Look for a pattern like "anything_sdknumber.extension"
|
| /development/pdk/docs/porting/ |
| bluetooth.jd | 70 <p>To debug your bluetooth implementation, start by reading the logs (<code>adb logcat</code>) and look for ERRROR and WARNING messages regarding Bluetooth.
|
| /development/pdk/docs/source/ |
| code-style.jd | 75 : Look at what's around you!
218 The imports people want to look at first tend to be at the top (android)The imports people want to look at least tend to be at the bottom (java)Humans can easily follow the styleThe IDE's can follow the style
352 <p>Our parting thought: BE CONSISTENT. If you're editing code, take a few minutes to look at the code around you and determine its style. If they use spaces around their if clauses, you should too. If their comments have little boxes of stars around them, make your comments have little boxes of stars around them too.
|
| /development/samples/SampleSyncAdapter/src/com/example/android/samplesync/platform/ |
| ContactManager.java | 108 // Look up the user's sample SyncAdapter data row
|
| /development/simulator/app/ |
| Preferences.cpp | 159 * Look up the name. If it doesn't exist, add it.
|
| /development/tools/apkcheck/ |
| README.txt | 92 the enumeration values. This makes it look like an APK is referring
|
| /device/sample/frameworks/PlatformLibrary/jni/ |
| PlatformLibrary.cpp | 229 /* look up the class */
|
| /external/bluetooth/bluez/src/ |
| hcid.conf.5.in | 120 In practice, most Bluetooth clients scan their surroundings in two successive steps: they first look for all bluetooth devices around them and find out their "class". You can do this on Linux with the \fBhcitool scan\fP command. Then, they use SDP in order to check if a device in a given class offers the type of service that they want.
|
| /external/bluetooth/glib/ |
| README.in | 38 looking at the given URI, the application will now need to look at
|
| /external/bluetooth/glib/gio/xdgmime/ |
| xdgmimeglob.c | 195 /* Look for the first character of text in glob_hash_node, and insert it if we
|
| /external/bluetooth/glib/po/ |
| Makefile.in.in | 10 # instead of PACKAGE and to look for po2tbl in ./ not in intl/
|
| /external/bzip2/ |
| README | 76 on the master web site (http://www.bzip.org). Look there. However
|
| /external/dbus/dbus/ |
| dbus-userdb.c | 435 * Creates a new user database object used to look up and
|
| /external/dnsmasq/contrib/dynamic-dnsmasq/ |
| dynamic-dnsmasq.pl | 44 my $dnsmasqpidfile = "/var/run/dnsmasq.pid"; # if this doesn't exist, will look for process in /proc
|
| /external/dnsmasq/src/ |
| rfc2131.c | 214 /* look for RFC3527 Link selection sub-option */
218 /* look for RFC5107 server-identifier-override */
602 /* dhcp-match. If we have hex-and-wildcards, look for a left-anchored match.
603 Otherwise assume the option is an array, and look for a matching element.
[all...] |
| /external/e2fsprogs/intl/ |
| localcharset.c | 347 /* Look for the possible @... trailer and remove it, if any. */
|
| localealias.c | 277 /* Now look for the beginning of the value. */
|
| /external/e2fsprogs/lib/ext2fs/ |
| dosio.c | 294 * Now that we know all we need, let's look for the partition
|
| /external/e2fsprogs/misc/ |
| findsuper.c | 20 * of the kernel include files to find anything I could look for in msdos.
|
| /external/elfutils/libebl/ |
| eblopenbackend.c | 202 /* XXX Currently all we do is to look at 'e_machine' value in the
|
| /external/freetype/include/freetype/config/ |
| ftconfig.h | 224 /* look up an integer type that is at least 32 bits */
|
