Home
last modified time | relevance | path

Searched refs:standard (Results 1 – 25 of 759) sorted by relevance

12345678910>>...31

/external/icu4c/test/cintltst/
Dstdnmtst.c38 static int dotestname(const char *name, const char *standard, const char *expected) { in dotestname() argument
45 tag = ucnv_getStandardName(name, standard, &error); in dotestname()
47 log_err_status(error, "FAIL: could not find %s standard name for %s\n", standard, name); in dotestname()
50 … log_err("FAIL: expected %s for %s standard name for %s, got %s\n", expected, standard, name, tag); in dotestname()
66 const char *standard; in TestStandardName() local
69 standard = ucnv_getStandard(i, &err); in TestStandardName()
73 } else if (!standard || !*standard) { in TestStandardName()
74 log_err("FAIL: %s standard name at index %d\n", (standard ? "empty" : in TestStandardName()
114 static int dotestconv(const char *name, const char *standard, const char *expected) { in dotestconv() argument
121 tag = ucnv_getCanonicalName(name, standard, &error); in dotestconv()
[all …]
/external/hyphenation/
DREADME.nonstandard1 Non-standard hyphenation
4 Some languages use non-standard hyphenation; `discretionary'
13 non-standard hyphenation patterns. For example:
32 Unfortunatelly, now the conversion step can generate bad non-standard
33 patterns (non-standard -> standard pattern conversion), so using
36 patterns resulting bad non-standard hyphenation in a few cases. Using narrow
39 Syntax of the non-standard hyphenation patterns
72 - only the greater value guarantees the win (don't mix non-standard and
73 non-standard patterns with the same value, for example
96 There hasn't been extended PatGen pattern generator for non-standard
[all …]
/external/llvm/docs/CommandGuide/
Dllvm-as.pod15 into a file or to standard output.
18 standard input.
21 B<llvm-as> sends its output to a file or standard output by following
28 If the input is standard input, then the output is standard output.
60 sends its output to standard output.
Dllvm-dis.pod17 input from standard input.
19 If the input is being read from standard input, then B<llvm-dis>
20 will send its output to standard output by default. Otherwise, the
43 to standard output.
Dopt.pod19 source. It will usually print the results on standard output, but in a few
20 cases, it will print output to standard error or generate a file with the
31 input from standard input. Inputs can be in either the LLVM assembly language
35 writes its output to the standard output.
68 This is short hand for a standard list of I<compile time optimization> passes.
78 removes the inlining pass from the standard list.
110 Record the amount of time needed for each pass and print it to standard
Dllvm-link.pod14 single LLVM bitcode file. It writes the output file to standard output, unless
43 write its output to standard output.
52 bitcode file to standard error.
/external/fdlibm/
Dreadme32 3. Compiler failure on non-standard code
35 are not standard C and cause some optimizing compilers (e.g. GCC)
118 create a multi-standard compliant FDLIBM. In this case, each
119 function in FDLIBM is actually a standard compliant wrapper
149 function to comply to the standard specified by the value
162 multi-standard compliant (supports IEEE,XOPEN,POSIX/ANSI,SVID).
169 To create a multi-standard compliant libm, use
170 make "CFLAGS = -D_IEEE_MODE" --- multi-standard fdlibm: default
172 make "CFLAGS = -D_XOPEN_MODE" --- multi-standard fdlibm: default
174 make "CFLAGS = -D_POSIX_MODE" --- multi-standard fdlibm: default
[all …]
/external/chromium/chrome/browser/ui/cocoa/
Dstyled_text_field_unittest.mm125 // the standard focusing machinery, or by -resetFieldEditorFrameIfNeeded.
127 // Capture the editor frame resulting from the standard focus machinery.
140 // in the same frame as the standard focus machinery.
147 // the standard focusing machinery, or by -resetFieldEditorFrameIfNeeded.
155 // Capture the editor frame resulting from the standard focus machinery.
166 // result in the same frame as the standard focus machinery.
173 // the standard focusing machinery, or by -resetFieldEditorFrameIfNeeded.
181 // Capture the editor frame resulting from the standard focus machinery.
192 // result in the same frame as the standard focus machinery.
/external/icu4c/data/zone/
Dit.txt461 ls{"Ora standard Sudafrica"}
478 ls{"Ora standard centrale USA"}
483 ls{"Ora standard orientale USA"}
488 ls{"Ora standard sulle Montagne Rocciose USA"}
493 ls{"Ora standard della costa del Pacifico USA"}
513 ls{"Ora standard dell'Atlantico"}
518 ls{"Ora standard dell'Australia (centrale)"}
523 ls{"Ora standard dell'Australia (centroccidentale)"}
528 ls{"Ora standard dell'Australia (orientale)"}
533 ls{"Ora standard dell'Australia (occidentale)"}
[all …]
Dro.txt1164 ls{"Ora standard în zona Alaska"}
1169 ls{"Ora standard în zona Alaska-Hawaii"}
1179 ls{"Ora standard centrală"}
1184 ls{"Ora standard orientală"}
1189 ls{"Ora standard în zona montană"}
1194 ls{"Ora standard în zona Pacific"}
1204 ls{"Ora standard arabă"}
1223 ls{"Ora standard în zona Atlantic"}
1228 ls{"Ora standard a Australiei Centrale"}
1233 ls{"Ora standard a Australiei Central Occidentale"}
[all …]
/external/linux-tools-perf/Documentation/
Dperf-help.txt17 on the standard output.
20 printed on the standard output.
33 Prints all the available commands on the standard output. This
/external/valgrind/main/docs/internals/
Dwhy-no-libc.txt5 Subject: Re: [Valgrind-developers] Using standard C library in valgrind tool
10 IS> I would like to write a valgrind tool that uses the standard c
34 that are the reason Valgrind tools don't link with the standard
45 thread-local storage (which I think is standard these days). Glibc now
57 So if you need C standard library functionality that isn't covered by
58 the Valgrind core's somewhat non-standard subset, you'll have to get
/external/libvpx/nestegg/halloc/
DREADME4 Hierarchical memory heap interface - an extension to standard
28 * improved standard compliance thanks to the feedback
32 array, which happened to be common, but non-standard
/external/astl/include/
Diostream37 * Declaration of the standard stream objects.
52 extern ostream cout; // Linked to standard output
53 extern ostream cerr; // Linked to standard error (unbuffered)
56 // this static variable. Its construction ensures that the standard
/external/icu4c/data/coll/
Droot.txt16 default{"standard"}
96 standard{
/external/qemu/distrib/sdl-1.2.12/src/video/Xext/
DREADME2 The reason these libraries are built outside of the standard XFree86
7 Linux platforms. Since these libraries haven't become standard yet,
/external/zlib/contrib/iostream3/
DREADME15 The new classes are as standard-compliant as possible, closely following the
16 approach of the standard library's fstream classes. It compiles under gcc versions
17 3.2 and 3.3, but not under gcc 2.xx. This is mainly due to changes in the standard
/external/icu4c/tools/gencnval/
Dgencnval.c166 addAlias(const char *alias, uint16_t standard, uint16_t converter, UBool defaultName);
645 addAlias(const char *alias, uint16_t standard, uint16_t converter, UBool defaultName) { in addAlias() argument
651 if(standard>=MAX_TAG_COUNT) { in addAlias()
659 aliasList = &tags[standard].aliasList[converter]; in addAlias()
673 if (standard == ALL_TAG_NUM && GET_ALIAS_STR(converters[converter].converter) != alias) { in addAlias()
689 if (standard != ALL_TAG_NUM) { in addAlias()
692 for (idx2 = 0; idx2 < tags[standard].aliasList[idx].aliasCount; idx2++) { in addAlias()
693 uint16_t aliasNum = tags[standard].aliasList[idx].aliases[idx2]; in addAlias()
706 GET_TAG_STR(tags[standard].tag), in addAlias()
712 GET_TAG_STR(tags[standard].tag), in addAlias()
[all …]
/external/clang/include/clang/Frontend/
DLangStandards.def16 /// \param IDENT - The name of the standard as a C++ identifier.
17 /// \param NAME - The name of the standard.
18 /// \param DESC - A short description of the standard.
19 /// \param FEATURES - The standard features as flags, these are enums from the
/external/antlr/antlr-3.4/runtime/C/doxygen/
Datsections.dox59 /// compile correctly on any standard C compiler (assuming, of course, that you type in valid C cod…
89 /// the code they encapsulate to be placed in the generated .h file, \b after the standard
93 /// statement to cause your grammar code to include some standard definitions. Because you
116 /// the code they encapsulate to be placed in the generated .h file, \b before the standard
120 /// in the code before the standard ANTLR runtime includes defined them. This allows you
130 /// file (which includes the standard ANTLR3C library includes.
133 /// generated include and by the standard ANTLR3 includes. This is a good place to <code>\#undef</c…
/external/stlport/etc/
DSTLport-4.5.3.spec3 Summary: Complete C++ standard library
23 Summary: Complete C++ standard library header files and libraries
29 C++ standard library, including <complex> and SGI STL iostreams. If you
DSTLport-4.6.spec3 Summary: Complete C++ standard library
23 Summary: Complete C++ standard library header files and libraries
29 C++ standard library, including <complex> and SGI STL iostreams. If you
DSTLport-4.5.1.spec3 Summary: Complete C++ standard library
23 Summary: Complete C++ standard library header files and libraries
29 C++ standard library, including <complex> and SGI STL iostreams. If you
/external/antlr/antlr-3.4/antlr3-maven-plugin/src/site/apt/
Dindex.apt15 The job of the plugin is essentially to tell the standard ANTLR parser generator where the
39 As with all Maven plugins, this plugin will automatically default to standard locations
40 for your grammar and import files. Organizing your source code to reflect this standard
41 layout will greatly reduce the configuration effort required. The standard layout lookd
/external/expat/doc/
Dxmlwf.sgml90 input file will be read from standard input.
178 coming from standard input. Therefore, you must be careful that the
257 when reading from standard input.
374 reading from standard input.
383 the problem to standard output. If a file is well formed,
392 According to the W3C standard, an XML file without a
401 standard output.
404 The errors should go to standard error, not standard output.
408 output to standard output rather than forcing the user to send

12345678910>>...31