| /prebuilt/ndk/android-ndk-r5/sources/cxx-stl/gnu-libstdc++/include/bits/ |
| istream.tcc | 664 // 60. What is a formatted input function?
697 // 60. What is a formatted input function?
|
| locale_facets_nonio.tcc | 480 // Fit formatted digits into the required pattern.
534 // Write resulting, fully-formatted string to output iterator.
[all...] |
| /prebuilt/ndk/android-ndk-r6/sources/cxx-stl/gnu-libstdc++/include/bits/ |
| istream.tcc | 664 // 60. What is a formatted input function?
697 // 60. What is a formatted input function?
|
| locale_facets_nonio.tcc | 480 // Fit formatted digits into the required pattern.
534 // Write resulting, fully-formatted string to output iterator.
[all...] |
| /sdk/emulator/gps/ |
| gps_qemu.c | 294 D("date not properly formatted: '%.*s'", tok.end-tok.p, tok.p);
302 D("date not properly formatted: '%.*s'", tok.end-tok.p, tok.p);
|
| /external/icu4c/test/cintltst/ |
| cnumtst.c | 793 log_verbose("formatted %d as '%s', length: %d\n", value, logbuf, len);
877 if (fieldPos.beginIndex != 26) { /* index of "." in formatted number *
[all...] |
| /external/libpcap/doc/ |
| pcap.xml | 192 <t>Options: optionally, a list of options (formatted according to the rules defined in <xref target="sectionopt"/>) can be present.</t>
249 <t>Options: optionally, a list of options (formatted according to the rules defined in <xref target="sectionopt"/>) can be present.</t>
362 <t>Options: optionally, a list of options (formatted according to the rules defined in <xref target="sectionopt"/>) can be present.</t>
455 <t>After the list or Name Resolution Records, optionally, a list of options (formatted according to the rules defined in <xref target="sectionopt"/>) can be present.</t>
519 <t>Options: optionally, a list of options (formatted according to the rules defined in <xref target="sectionopt"/>) can be present.</t>
[all...] |
| /external/markdown/MarkdownTest/Tests_2004/ |
| Markdown Documentation - Syntax.html | 52 <p>Readability, however, is emphasized above all else. A Markdown-formatted
475 <p>Pre-formatted code blocks are used for writing about programming or
776 Unlike a pre-formatted code block, a code span indicates code within a
|
| Markdown Documentation - Syntax.text-out | 65 Markdown-formatted document should be publishable as-is, as plain
487 <p>Pre-formatted code blocks are used for writing about programming
789 (<code>`</code>). Unlike a pre-formatted code block, a code span
|
| Markdown Documentation - Syntax.text-res | 65 Markdown-formatted document should be publishable as-is, as plain
487 <p>Pre-formatted code blocks are used for writing about programming
789 (<code>`</code>). Unlike a pre-formatted code block, a code span
|
| /external/markdown/MarkdownTest/Tests_2007/ |
| Markdown Documentation - Syntax.html | 52 <p>Readability, however, is emphasized above all else. A Markdown-formatted
475 <p>Pre-formatted code blocks are used for writing about programming or
776 Unlike a pre-formatted code block, a code span indicates code within a
|
| /external/markdown/tests/extensions-x-def_list/ |
| markdown-syntax.html | 47 <p>Readability, however, is emphasized above all else. A Markdown-formatted
377 <p>Pre-formatted code blocks are used for writing about programming or
607 Unlike a pre-formatted code block, a code span indicates code within a
|
| /external/markdown/tests/extensions-x-toc/ |
| syntax-toc.html | 35 <p>Readability, however, is emphasized above all else. A Markdown-formatted
357 <p>Pre-formatted code blocks are used for writing about programming or
582 Unlike a pre-formatted code block, a code span indicates code within a
|
| /external/markdown/tests/markdown-test/ |
| markdown-syntax.html | 47 <p>Readability, however, is emphasized above all else. A Markdown-formatted
377 <p>Pre-formatted code blocks are used for writing about programming or
607 Unlike a pre-formatted code block, a code span indicates code within a
|
| /external/webkit/Tools/android/flex-2.5.4a/MISC/ |
| parse.c | 441 /* format_synerr - write out formatted syntax error */
463 /* format_warn - write out formatted warning */
483 /* format_pinpoint_message - write out a message formatted with one string,
[all...] |
| /prebuilt/linux-x86/toolchain/i686-linux-glibc2.7-4.4.3/i686-linux/include/c++/4.4.3/bits/ |
| locale_facets_nonio.tcc | 480 // Fit formatted digits into the required pattern.
534 // Write resulting, fully-formatted string to output iterator.
[all...] |
| /cts/tests/tests/telephony/src/android/telephony/cts/ |
| PhoneNumberUtilsTest.java | 333 // Test formatNumber(String). Only numbers begin with +1 or +81 can be formatted.
|
| /dalvik/vm/ |
| Exception.h | 201 * Print a formatted version of a raw stack trace to the log file.
|
| /development/ndk/platforms/android-9/samples/native-audio/jni/ |
| native-audio-jni.c | 28 // for __android_log_print(ANDROID_LOG_INFO, "YourApp", "formatted message");
|
| /development/pdk/docs/source/ |
| download.jd | 67 <p>Android must be built on a case-sensitive file system because the sources contain files that differ only in case. We recommend that you build Android on a partition that has been formatted with the journaled file system HFS+. HFS+ is required to successfully build Mac OS applications such as the Android Emulator for OS X.</p>
|
| /external/apache-xml/src/main/java/org/apache/xml/serializer/ |
| Encodings.java | 308 * System property "encodings" formatted using URL syntax may define an
|
| /external/bluetooth/glib/docs/reference/glib/tmpl/ |
| testing.sgml | 57 facilitate running tests and producing nicely formatted test reports.
|
| /external/bluetooth/glib/tests/ |
| date-test.c | 138 TEST("Successfully parsed a %x-formatted string",
|
| testgdate.c | 145 TEST("Successfully parsed a %x-formatted string",
|
| /external/chromium/chrome/browser/ |
| crash_handler_host_linux.cc | 265 // /proc/[pid]/syscall is formatted as follows:
|
