Searched refs:standardization (Results 1 – 25 of 36) sorted by relevance
12
/third_party/jsframework/runtime/main/manage/event/ |
D | TaskCenter.ts | 142 public standardization(arg: any): any { method in TaskCenter 147 ans[key] = this.standardization(arg[key]); 153 return arg.map(i => this.standardization(i)); 172 args = args.map(arg => this.standardization(arg));
|
/third_party/boost/libs/stl_interfaces/doc/ |
D | stl_interfaces.qbk | 14 A string and rope library targeting standardization. 78 standardization, and the changes required to make it C++11-compatible were
|
/third_party/node/deps/npm/test/fixtures/ |
D | third-party.md | 17 The limited permissions are granted through the standardization phase and
|
/third_party/boost/libs/system/doc/system/ |
D | introduction.adoc | 48 during standardization. The Boost implementation has been tracking those changes.
|
/third_party/wayland-protocols_standard/ |
D | GOVERNANCE.md | 4 the broader process for standardization of protocol extensions in the Wayland 11 standardization.
|
/third_party/boost/libs/stl_interfaces/ |
D | README.md | 7 targeting standardization. This library requires at least C++14.
|
/third_party/icu/docs/userguide/format_parse/numbers/ |
D | rbnf.md | 101 > :point_right: **Note**: There is no standardization of rule set names, so you must either query t…
|
/third_party/boost/libs/regex/doc/ |
D | history.qbk | 191 …en expression parsing code, and traits class support; now conforms to the standardization proposal. 211 * Deprecated all interfaces that are not part of the regular expression standardization proposal.
|
D | concepts.qbk | 41 [basic_regex]: a minimal interface (which is part of the regex standardization proposal),
|
D | old_regex.qbk | 12 part of the regular expression standardization proposal. This type still
|
/third_party/typescript_eslint/packages/eslint-plugin/docs/rules/ |
D | ban-types.md | 69 …ns provide a set of "best practices", intended to provide safety and standardization in your codeb…
|
/third_party/boost/libs/beast/doc/qbk/08_design/ |
D | 4_faq.qbk | 39 reduce its appeal for standardization. 95 is the author's goal to propose this library for standardization.
|
/third_party/mbedtls/docs/proposed/ |
D | psa-conditional-inclusion-c.md | 6 This is currently a proposal for Mbed TLS. It is not currently on track for standardization in PSA. 182 ## PSA standardization
|
/third_party/libphonenumber/ |
D | FAQ.md | 122 with varying standardization practices in different regions. 193 The reason for Libphonenumber to not provide M2M support is related to the lack of standardization … 197 …ell as assuming standard cost. This expectation is broken by the lack of M2M standardization today.
|
/third_party/boost/libs/iterator/doc/quickbook/ |
D | iterator.qbk | 103 adaptors] mentioned below have been proposed for standardization
|
/third_party/boost/libs/iterator/doc/ |
D | index.rst | 118 adaptors`_ mentioned below have been proposed for standardization;
|
/third_party/skia/third_party/externals/opengl-registry/extensions/KHR/ |
D | KHR_blend_equation_advanced.txt | 700 RESOLVED: During standardization of this extensions, the set of 1056 Add issues for the spec issues discussed during standardization in
|
/third_party/openGLES/extensions/KHR/ |
D | KHR_blend_equation_advanced.txt | 710 RESOLVED: During standardization of this extensions, the set of 1066 Add issues for the spec issues discussed during standardization in
|
/third_party/ltp/scripts/ |
D | spelling.txt | 1378 standartization||standardization
|
/third_party/python/Doc/library/ |
D | exceptions.rst | 368 range. Because of the lack of standardization of floating point exception
|
/third_party/pulseaudio/src/modules/rtp/ |
D | rfc3551.txt | 22 Official Protocol Standards" (STD 1) for the standardization state 2266 coding standardization".
|
D | rfc2327.txt | 20 Official Protocol Standards" (STD 1) for the standardization state
|
/third_party/boost/libs/container/doc/ |
D | container.qbk | 143 do this, why the standardization committee banned it even though they knew it was useful, and what 146 ["['In 1997, shortly before the C++ Standard was completed, the standardization committee received a
|
/third_party/skia/third_party/externals/brotli/tests/testdata/ |
D | lcet10.txt | 3837 AIIM's standards program * Domain of AIIM's standardization work * AIIM's 3839 Categories of EIM standardization where AIIM standards are being 3846 for standardization in which AIIM is active. 3851 maintains both its library and business-image management standardization 3853 standardization (EIM). 3870 BARONAS then illustrated the domain of AIIM's standardization work. For 3875 the international standardization process. 3906 BARONAS next outlined the four categories of EIM standardization in which 5762 standardization or distribution of responsibility.
|
/third_party/tzdata/ |
D | australasia | 2004 # Howse writes (p 153) that after the 1879 standardization on Antipodean
|
12