Home	Sort by relevance Sort by last modified time

Full Search Definition Symbol File Path History   | | Help

    Searched full:calling (Results 401 - 425 of 3111) sorted by null

<<11121314151617181920>>

/hardware/ti/wlan/wl1271/TWD/FW_Transfer/Export_Inc/
CmdMBox_api.h	64 * Calling this function creates a CmdMbox object 78 * Calling this function destroys a CmdMbox object
FwEvent_api.h	54 * Calling this function creates a FwEvent object 68 * Calling this function destroys a FwEvent object
/packages/apps/Email/src/org/apache/james/mime4j/field/address/parser/
ParseException.java	22 * calling the method generateParseException in the generated 32 * in the generated parser. Calling this constructor generates
/packages/apps/Email/src/org/apache/james/mime4j/field/contenttype/parser/
ParseException.java	22 * calling the method generateParseException in the generated 32 * in the generated parser. Calling this constructor generates
/packages/apps/Email/src/org/apache/james/mime4j/field/datetime/parser/
ParseException.java	22 * calling the method generateParseException in the generated 32 * in the generated parser. Calling this constructor generates
/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/lib/gcc/arm-eabi/4.4.0/plugin/include/config/arm/
bpabi.h	48 calling convention. */ 156 This is OK because it uses a special calling convention anyway. */
/system/wlan/ti/sta_dk_4_0_4_32/common/src/TNETW_Driver/TNETWIF/Inc/
TNETWArb.h	71 TI_HANDLE instance_handle; /* The handle of the module to be used when calling back the client */ 72 TNETWIF_callback_t instance_callback; /* The handler of the module to be used when calling back the client */
/system/wlan/ti/wilink_6_1/TWD/Ctrl/Export_Inc/
CmdQueue_api.h	67 * Calling this function creates a CmdQueue object 81 * Calling this function destroys the cmdQueue object
/system/wlan/ti/wilink_6_1/TWD/FW_Transfer/Export_Inc/
CmdMBox_api.h	64 * Calling this function creates a CmdMbox object 78 * Calling this function destroys a CmdMbox object
/external/bluetooth/glib/docs/reference/glib/tmpl/
threads.sgml	52 application's main() before calling any GLib functions or functions in 55 After calling g_thread_init(), GLib is completely 179 the thread system by calling g_thread_init(). Most of the time you 191 calling g_thread_init(). 316 calling g_thread_join(). Otherwise the thread will just disappear when 347 calling g_thread_join(). Otherwise the thread will just disappear when 397 This functions returns the #GThread corresponding to the calling thread. 455 ignored. Calling 467 is equivalent to calling 591 calling g_thread_init() first, then you can not use a #GMutex, a     [all...]
/external/skia/include/core/
SkFontHost.h	42 cache and return the same instance (but calling typeface->ref(), since the 43 caller is always responsible for calling unref() on each instance that is 76 calling unref() on the typeface when they are finished with it. 87 the caller is responsible for calling unref() when it is no longer used. 94 Returning false is similar to calling OpenStream with an invalid ID,
/frameworks/base/core/java/android/app/
Instrumentation.java	878 * objects by hand and calling {@link #sendKeySync}. The event appears     [all...]
/external/kernel-headers/original/asm-x86/
uaccess_32.h	80 * checks that the pointer is in the user space range - after calling 165 * Strange magic calling convention: pointer in %ecx, 241 * Caller must check the pointer with access_ok() before calling this 265 * Caller must check the pointer with access_ok() before calling this 409 * the specified block with access_ok() before calling this function. 449 * the specified block with access_ok() before calling this function. 496 * the specified block with access_ok() before calling this function.
/external/zlib/win32/
DLL_FAQ.txt	29 * The calling convention of functions is "C" (CDECL). 85 - In principle, you can do it by assigning calling convention 89 You have to find out first what kind of calling convention is 134 6. I see that the ZLIB1.DLL functions use the "C" (CDECL) calling 174 The calling convention issues are also important when using 177 initially on Unix, and relying on the C calling convention. 221 are calling standard C functions), must link to the same
/external/bluetooth/glib/glib/
ghash.c	205 * are equal so we can avoid calling the full-blown 280 * are equal so we can avoid calling the full-blown 534 * @hash_table. Modifying the hash table after calling this function 681 * from its associated #GHashTable, without calling the key and value 799 * for example before calling g_hash_table_remove(). 960 * Do a lookup of @key and remove it if it is found, calling the 1017 * calling the key and value destroy functions. 1060 * without calling the key and value destroy functions. 1088 * Iterates over every node in the table, calling @func with the key     [all...]
/dalvik/libcore/xml/src/main/java/org/xmlpull/v1/
XmlPullParser.java	35 * can be determined by calling the 152 * This event type can only be observed by calling getEvent() 164 * <p><strong>NOTE:</strong> calling again 214 * Character data was read and will is available by calling getText(). 221 * Also, when the state was reached by calling next(), the text value will 242 * by calling getText(). 252 * only. The entity name is available by calling getName(). If available, 253 * the replacement text can be obtained by calling getText(); otherwise, 272 * The ignorable whitespace string is available by calling getText() 274 * <p><strong>NOTE:</strong> this is different from calling th     [all...]
/development/samples/SpinnerTest/src/com/android/example/spinner/test/
SpinnerActivityTest.java	257 // Halt the Activity by calling Activity.finish() on it 261 // Restart the activity by calling ActivityInstrumentationTestCase2.getActivity() 310 * This analogous to calling finish() in the testStateDestroy() method.
/external/dbus/dbus/
dbus-dataslot.c	82 _dbus_warn_check_failed ("D-Bus threads were initialized after first using the D-Bus library. If your application does not directly initialize threads or use D-Bus, keep in mind that some library or plugin may have used D-Bus or initialized threads behind your back. You can often fix this problem by calling dbus_init_threads() or dbus_g_threads_init() early in your main() method, before D-Bus is used.\n"); 319 * Frees all data slots contained in the list, calling 342 * in it, calling application-provided free functions
/external/expat/
Changes	2 - Fixed bugs #1515266, 1515600: The character data handler's calling 49 - Introduced an XMLCALL macro to control the calling 52 implementations in code compiled with a calling convention
/external/icu4c/layoutex/layout/
plruns.h	152 * If the <code>pl_fontRuns</code> object was not created by calling 285 * If the <code>pl_valueRuns</code> object was not created by calling 417 * If the <code>pl_localeRuns</code> object was not created by calling
/external/iptables/
ip6tables-restore.c	181 DEBUGP("Calling commit\n"); 184 DEBUGP("Not calling commit, testing\n"); 401 DEBUGP("calling do_command6(%u, argv, &%s, handle):\n",
iptables-restore.c	184 DEBUGP("Calling commit\n"); 187 DEBUGP("Not calling commit, testing\n"); 404 DEBUGP("calling do_command(%u, argv, &%s, handle):\n",
/external/opencore/pvmi/pvmf/include/
pvmf_timedtext.h	211 * takes care of calling the destructor for PVMFTimedTextMediaData 372 * takes care of calling the destructor for PVMFTimedTextSampleEntry 394 * takes care of calling the destructor for PVMFTimedTextSampleEntry
/external/qemu/docs/
CHAR-DEVICES.TXT	138 to a CharDriverState (by calling qemu_chr_write() explicitely) and can also 170 Note also that calling qemu_chr_add_handler() on the CharBuffer will do the 196 iteration by calling the can_read/read functions of the corresponding user,
/external/wpa_supplicant_6/wpa_supplicant/
README-WPS	99 control interface request, e.g., by calling wpa_cli: 112 request, e.g., by calling wpa_cli: 125 over the control interface, e.g., by calling wpa_cli:

Completed in 133 milliseconds

<<11121314151617181920>>