Home
last modified time | relevance | path

Searched refs:coding (Results 1 – 25 of 397) sorted by relevance

12345678910>>...16

/external/tensorflow/tensorflow/core/lib/core/
DBUILD59 name = "coding",
60 hdrs = ["coding.h"],
62 "//tensorflow/core/platform:coding",
156 "coding.h",
187 "coding.h",
270 "coding.h",
/external/kmod/
DCODING-STYLE1 Every project has its coding style, and kmod is not an exception. This
2 document describes the preferred coding style for kmod code, in order to keep
8 First of all, kmod coding style must follow every rule for Linux kernel
18 Besides the kernel coding style above, kmod coding style is heavily based on
/external/arm-trusted-firmware/docs/process/
Dindex.rst11 coding-style
12 coding-guidelines
/external/python/cpython3/Lib/test/
Dtokenize_tests-latin1-coding-cookie-and-utf8-bom-sig.txt1 # -*- coding: latin1 -*-
4 # are made! Also note that the coding cookie above conflicts with
Dtokenize_tests-utf8-coding-cookie-and-utf8-bom-sig.txt1 # -*- coding: utf-8 -*-
Dtokenize_tests-utf8-coding-cookie-and-no-utf8-bom-sig.txt1 # -*- coding: utf-8 -*-
/external/libcups/cups/
Dhttp.c649 if (http->coding) in httpFlush()
1656 if (http->coding >= _HTTP_CODING_GUNZIP) in httpPeek()
1684 (http->coding == _HTTP_CODING_IDENTITY || in httpPeek()
1685 (http->coding >= _HTTP_CODING_GUNZIP && ((z_stream *)http->stream)->avail_in == 0))) in httpPeek()
1728 if (http->coding >= _HTTP_CODING_GUNZIP) in httpPeek()
1943 …ng=" CUPS_LLFMT, (void *)http, (void *)buffer, CUPS_LLCAST length, http->coding, http->data_encodi… in httpRead2()
1958 if (http->coding >= _HTTP_CODING_GUNZIP) in httpRead2()
2107 (http->coding == _HTTP_CODING_IDENTITY || in httpRead2()
2108 (http->coding >= _HTTP_CODING_GUNZIP && ((z_stream *)http->stream)->avail_in == 0)) && in httpRead2()
2115 if (http->coding >= _HTTP_CODING_GUNZIP) in httpRead2()
[all …]
/external/ltp/testcases/open_posix_testsuite/Documentation/
DHOWTO_CodingGuidelines1 This document describes the coding guidelines for this project.
6 demonstrates the bug, it makes sense to follow the coding guidelines
/external/tensorflow/tensorflow/core/lib/io/
DBUILD37 "//tensorflow/core/lib/core:coding",
74 "//tensorflow/core/lib/core:coding",
122 "//tensorflow/core/lib/core:coding",
154 "//tensorflow/core/lib/core:coding",
175 "//tensorflow/core/lib/core:coding",
216 "//tensorflow/core/platform:coding",
237 "//tensorflow/core/lib/core:coding",
/external/llvm-project/clang/docs/
DLibFormat.rst47 /// Returns a format style complying with the LLVM coding standards:
59 /// Returns a format style complying with the GNU coding standards:
64 /// https://firefox-source-docs.mozilla.org/code-quality/coding-style/index.html
/external/python/cryptography/docs/
Dlimitations.rst14 `CERT secure coding guidelines`_ assesses this issue as "Severity: medium,
19 .. _`CERT secure coding guidelines`: https://www.securecoding.cert.org/confluence/display/c/MEM03-C…
/external/llvm-project/parallel-libs/
DREADME.rst39 1. Adhere to the LLVM coding standards.
46 Libraries in `parallel-libs` will match the LLVM coding standards. For existing
50 will be allowed for new libraries to meet the LLVM coding standards.
52 Additional exceptions to strict adherence to the LLVM coding standards may be
/external/llvm-project/clang-tools-extra/docs/clang-tidy/
Dindex.rst70 ``darwin-`` Checks related to Darwin coding conventions.
71 ``fuchsia-`` Checks related to Fuchsia coding conventions.
72 ``google-`` Checks related to Google coding conventions.
74 ``linuxkernel-`` Checks related to the Linux Kernel coding conventions.
75 ``llvm-`` Checks related to the LLVM coding conventions.
76 ``llvmlibc-`` Checks related to the LLVM-libc coding standards.
81 ``objc-`` Checks related to Objective-C coding conventions.
85 relate to any particular coding style.
87 relate to any particular coding style.
88 ``zircon-`` Checks related to Zircon kernel coding conventions.
[all …]
/external/libxml2/result/noent/
Dintsubset2.xml.sax249 The character itself in UTF8 coding.
63 The cp_type attribute states the coding standard applying to the
65 jis208 - JIS X 0208-1997 - kuten coding (nn-nn)
66 jis212 - JIS X 0212-1990 - kuten coding (nn-nn)
67 jis213 - JIS X 0213-2000 - kuten coding (p-nn-nn)
68 ucs - Unicode 4.0 - hex coding (4 or 5 hexadecimal digits)
109 jis208 - in JIS X 0208 - kuten coding
110 jis212 - in JIS X 0212 - kuten coding
111 jis213 - in JIS X 0213 - kuten coding
/external/libxml2/result/
Dintsubset2.xml.sax49 The character itself in UTF8 coding.
63 The cp_type attribute states the coding standard applying to the
65 jis208 - JIS X 0208-1997 - kuten coding (nn-nn)
66 jis212 - JIS X 0212-1990 - kuten coding (nn-nn)
67 jis213 - JIS X 0213-2000 - kuten coding (p-nn-nn)
68 ucs - Unicode 4.0 - hex coding (4 or 5 hexadecimal digits)
109 jis208 - in JIS X 0208 - kuten coding
110 jis212 - in JIS X 0212 - kuten coding
111 jis213 - in JIS X 0213 - kuten coding
Dintsubset2.xml.sax249 The character itself in UTF8 coding.
63 The cp_type attribute states the coding standard applying to the
65 jis208 - JIS X 0208-1997 - kuten coding (nn-nn)
66 jis212 - JIS X 0212-1990 - kuten coding (nn-nn)
67 jis213 - JIS X 0213-2000 - kuten coding (p-nn-nn)
68 ucs - Unicode 4.0 - hex coding (4 or 5 hexadecimal digits)
109 jis208 - in JIS X 0208 - kuten coding
110 jis212 - in JIS X 0212 - kuten coding
111 jis213 - in JIS X 0213 - kuten coding
/external/arm-trusted-firmware/
D.editorconfig13 # (https://www.kernel.org/doc/html/v4.10/process/coding-style.html)
26 # Not specified, but implicit for "LINUX coding style".
/external/llvm-project/llvm/docs/Proposals/
DVariableNames.rst38 ... or more commonly use an acronym, despite the coding standard stating "Avoid
49 Many other coding guidelines [LLDB]_ [Google]_ [WebKit]_ [Qt]_ [Rust]_ [Swift]_
61 This work-in-progress proposal is to change the coding standard for variable
114 While switching coding standard will make it easier to use non-acronym names for
119 acronyms despite what the coding standard says, much as it is today.
183 1. Keep the current coding standard
187 Keep the current coding standard
190 Proponents of keeping the current coding standard (i.e. not transitioning at
200 The coding standard could allow both ``CamelCase`` and ``camelBack`` styles for
352 …entions https://llvm.org/svn/llvm-project/lldb/branches/release_39/www/lldb-coding-conventions.html
[all …]
/external/icu/icu4c/source/test/testdata/
Dencoded.utf16be1 // -*- coding: utf-16-be -*-
/external/grpc-grpc/test/core/end2end/fuzzers/server_fuzzer_corpus/
Dd297b3f84e3dee9f74bf1162718aff66a11a7f5c6 :authority localhost content-typeapplication/grpcgrpc-accept-enPRI * codingdeflate,identity,gz…
/external/clang/tools/scan-build-py/tests/functional/exec/
Dconfig.h.in1 /* -*- coding: utf-8 -*-
/external/clang/tools/scan-build-py/libear/
Dconfig.h.in1 /* -*- coding: utf-8 -*-
/external/llvm-project/clang/tools/scan-build-py/tests/functional/exec/
Dconfig.h.in1 /* -*- coding: utf-8 -*-
/external/llvm-project/clang/tools/scan-build-py/libear/
Dconfig.h.in1 /* -*- coding: utf-8 -*-
/external/fsverity-utils/
D.clang-format8 # Formatting settings to approximate the Linux kernel coding style.

12345678910>>...16