Searched
full:what (Results
401 -
425 of
4330) sorted by null
<<11121314151617181920>>
/dalvik/vm/jdwp/ |
JdwpEvent.h | 90 enum JdwpEventKind eventKind; /* what kind of event is this? */
|
/dalvik/vm/mterp/armv5te/ |
OP_CMPL_DOUBLE.S | 11 * on what value we'd like to return when one of the operands is NaN.
|
/dalvik/vm/mterp/cstubs/ |
stubdefs.c | 28 * Redefine what used to be local variable accesses into MterpGlue struct
|
/dalvik/vm/mterp/x86/ |
cvtfp_int.S | 6 * differs from what is delivered normally via the x86 fpu, so we have
|
/development/pdk/docs/source/ |
code-style.jd | 75 : Look at what's around you! 136 <p><b>What it is</b> 146 : we don't use finalizers. In most cases, you can do what you need from a finalizer with good exception handling. If you absolutely need it, define a close() method (or the like) and document exactly when that method needs to be called. See InputStream for an example. In this case it is appropriate but not required to print a short log message from the finalizer, as long as it is not expected to flood the logs. 155 <p><b>What it is</b> 167 : Makes it obvious what classes are actually used. Makes code more readable for maintainers. 174 <p>Every file should have a copyright statement at the top. Then a package statement and import statements should follow, each block separated by a blank line. And then there is the class or interface declaration. In the Javadoc comments, describe what the class or interface does. 178 contain a Javadoc comment with at least one sentence describing what the class or method does. This sentence should start with a 3rd person descriptive verb. Examples: 181 <p>You do not need to write Javadoc for trivial get and set methods such as setFoo() if all your Javadoc would say is "sets Foo". If the method does something more complex (such as enforcing a constraint or having an important side effect), then you must document it. And if it's not obvious what the property "Foo" means, you should document it. 220 What about static imports? 354 <p>The point of having style guidelines is to have a common vocabulary of coding, so people can concentrate on what you're saying, rather than on how you're saying it. We present global style rules here so people k (…) [all...] |
index.jd | 15 any particular release. To see what happens to your bug once you report it,
|
/development/samples/ApiDemos/src/com/example/android/apis/app/ |
ContactsFilterInstrumentation.java | 32 * process, for controlling and monitoring what it does.
|
ContactsSelectInstrumentation.java | 35 * process, for controlling and monitoring what it does.
|
CustomTitle.java | 57 * describe what is to be displayed in the screen.
|
NotificationDisplay.java | 42 * describe what is to be displayed in the screen.
|
SendResult.java | 39 * describe what is to be displayed in the screen.
|
/development/samples/SkeletonApp/ |
readme.txt | 16 This XML file describes to the Android platform what your application can do.
|
/development/samples/VoiceRecognitionService/ |
AndroidManifest.xml | 27 for the service is important to provide, as this is what will show
|
/development/simulator/app/ |
Preferences.h | 48 * what guarantees TinyXml makes wrt string lifetime (especially in
|
/external/bluetooth/bluez/src/ |
main.conf | 33 # What value should be assumed for the adapter Powered property when
|
/external/bluetooth/glib/gthread/ |
gthread-posix.c | 85 # define posix_error(what) (what) 89 # define posix_error(what) ((what) == -1 ? errno : 0)
|
/external/clearsilver/util/ |
neo_date.c | 77 /* Hefted from NCSA HTTPd src/util.c -- What a pain in the ass. */
|
/external/dbus/bus/ |
system.conf.in | 56 <!-- This is included last so local configuration can override what's
|
/external/dbus/test/data/valid-config-files/ |
system.conf | 56 <!-- This is included last so local configuration can override what's
|
/external/dnsmasq/contrib/port-forward/ |
dnsmasq-portforward | 25 # log what's going on.
|
/external/dropbear/ |
SMALL | 26 who will be connecting and what clients they will be using.
|
/external/dropbear/libtommath/ |
bn_mp_mul_2.c | 46 /* get what will be the *next* carry bit from the
|
/external/e2fsprogs/lib/e2p/ |
mntopts.c | 93 * parameter, if non-zero, allows the application to limit what
|
/external/easymock/src/org/easymock/ |
Capture.java | 23 * Will contain what was captured by the <code>capture()</code> matcher. Knows
|
/external/elfutils/ |
NOTES | 41 - what should happen if two sections in different files with the same
|
Completed in 174 milliseconds
<<11121314151617181920>>