| /external/wycheproof/ |
| local_repository_defs.bzl | 10 # see https://bazel.build/designs/2016/10/18/repository-invalidation.html
|
| /external/libcxx/www/ |
| atomic_design.html | 39 There are currently 3 designs under consideration. They differ in where most
41 should be identical (and conforming) for all three designs.
|
| /prebuilts/ndk/r16/sources/cxx-stl/llvm-libc++/www/ |
| atomic_design.html | 39 There are currently 3 designs under consideration. They differ in where most
41 should be identical (and conforming) for all three designs.
|
| /external/llvm/utils/lit/ |
| setup.py | 42 * Support for multiple test formats and test suite designs.
|
| /external/swiftshader/third_party/LLVM/utils/lit/ |
| setup.py | 35 * Support for multiple test formats and test suite designs.
|
| /prebuilts/misc/darwin-x86_64/freetype/include/freetype2/ |
| ftmm.h | 96 /* num_designs :: Number of designs; should be normally 2^num_axis */
98 /* allows for intermediate designs to be present. */
193 /* num_designs :: The number of designs; should be normally */
196 /* number of designs). */
|
| ftcffdrv.h | 86 * and Latin type designs. Even when the rasterizer uses greyscale
|
| /cts/tests/tests/permission/src/android/permission/cts/ |
| ServicePermissionTest.java | 28 * The security designs of many system features require that a special
|
| /external/python/cpython2/Demo/turtle/ |
| tdemo_lindenmayer_indian.py | 7 India, place designs, created by using rice
|
| tdemo_fractalcurves.py | 6 This program draws two fractal-curve-designs:
|
| /external/python/cpython3/Lib/turtledemo/ |
| lindenmayer.py | 7 India, place designs, created by using rice
|
| fractalcurves.py | 6 This program draws two fractal-curve-designs:
|
| /external/freetype/include/freetype/ |
| ftmm.h | 97 /* num_designs :: Number of designs; should be normally 2^num_axis */
99 /* allows for intermediate designs to be present. */
209 /* num_designs :: The number of designs; should be normally */
213 /* number of designs). */
[all...] |
| /external/replicaisland/ |
| README.TXT | 43 Genki Mine made all of the art, most of the levels layouts, all of the character designs, most of the sound, and also contributed to the game design.
|
| /external/tensorflow/tensorflow/docs_src/about/ |
| bib.md | 120 ?parameter server? designs the management of shared
|
| /external/v8/ |
| AUTHORS | 8 Sigma Designs Inc. <*@sdesigns.com>
|
| /prebuilts/go/darwin-x86/src/crypto/rsa/ |
| example_test.go | 30 // In these designs, when using PKCS#1 v1.5, it's vitally important to
|
| /prebuilts/go/linux-x86/src/crypto/rsa/ |
| example_test.go | 30 // In these designs, when using PKCS#1 v1.5, it's vitally important to
|
| /external/freetype/src/type1/ |
| t1load.c | 503 FT_Long* designs = map->design_points; local
512 design = ( designs[map->num_points - 1] - designs[0] ) / 2;
516 FT_Long p_design = designs[p];
543 the_blend = FT_MulDiv( design - designs[before],
545 designs[after] - designs[before] );
779 /* get the array of design tokens -- compute number of designs */
790 " incorrect number of designs: %d\n",
987 " incorrect number of designs: %d\n"
[all...] |
| /libcore/ojluni/src/main/java/java/util/concurrent/ |
| package-info.java | 120 * related concurrent designs.
173 * pipeline designs.
|
| CountedCompleter.java | 274 * divide and conquer designs is to have each subtask record its
331 * completion designs that combine results. This callback-style method
392 * forked, but instead serve as bits of plumbing in other designs;
|
| /external/llvm/include/llvm/ADT/ |
| iterator.h | 29 /// designs where this doesn't work well. It doesn't really force much added
|
| /external/protobuf/src/google/protobuf/compiler/ |
| code_generator.h | 93 // to encourage alternate designs.
|
| /prebuilts/tools/darwin-x86_64/protoc/include/google/protobuf/compiler/ |
| code_generator.h | 93 // to encourage alternate designs.
|
| /external/google-styleguide/ |
| xmlstyle.html | 351 Google XML Document Format Style Guide</h1><div style="text-align: center;">Version 1.0<br>Copyright Google 2008<br><br></div><h2>Introduction</h2>This document provides a set of guidelines for general use when designing new XML document formats (and to some extent XML documents as well; see Section 11). Document formats usually include both formal parts (DTDs, schemas) and parts expressed in normative English prose.<br><br>These guidelines apply to new designs, and are not intended to force retroactive changes in existing designs. When participating in the creation of public or private document format designs, the guidelines may be helpful but should not control the group consensus.<br><br>This guide is meant for the design of XML that is to be generated and consumed by machines rather than human beings. Its rules are <i>not applicable</i> to formats such as XHTML (which should be formatted as much like HTML as possible) or ODF which are meant to express rich text. A document that includes embedded content in XHTML or some other rich-text format, but also contains purely machine-interpretable portions, SHOULD follow this style guide for the machine-interpretable portions. It also does not affect XML document formats that are created by translations from proto buffers or through some other type of format.<br><br>Brief rationales have been added to most of the guidelines. They are maintained in the same document in hopes that they won't get out of date, but they are not considered normative.<br><br>The terms MUST, MUST NOT, SHOULD, SHOULD NOT, and MAY are used in this document in the sense of <a title="RFC 2119" href="https://www.ietf.org/rfc/rfc2119.txt" id="iecm">RFC 2119.</a><br> <br><h2>1. To design or not to design, that is the question<br></h2><ol><li>Attempt to reuse existing XML formats whenever possible, especially those which allow extensions. Creating an entirely new format should be done only with care and consideration; read <a title="Tim Bray's warnings" href="https://www.tbray.org/ongoing/When/200x/2006/01/08/No-New-XML-Languages" id="d3cy">Tim Bray's warnings</a> first. Try to get wide review of your format, from outside your organization as well, if possible. [<i>Rationale:</i> New document formats have a cost: they must be reviewed, documented, and learned by users.]<br><br></li><li>If you are reusing or extending an existing format, make <i>sensible</i>
360 restrictions on designs. The compact syntax is quite easy to read and
455 Attributes are more restrictive than elements, and all designs have some elements, so an all-element design is simplest -- which is not the same as best.
[all...] |
