| /third_party/ltp/testcases/kernel/controllers/freezer/ |
| D | 00_description.txt | 3 We initially try to freeze the cgroup but then try to cancel that.
5 state. We expect the process to still be alive as we cleanup the test.
9 The sleep process is frozen. We then kill the sleep process.
10 Then we unfreeze the sleep process and see what happens. We expect the
16 The sleep process is frozen. We then move the sleep process to a THAWED
17 cgroup. We expect moving the sleep process to fail.
22 part of. We then thaw the subshell process. We expect the unthawed
28 The sleep process is frozen. We then wait until the sleep process should
29 have exited. Then we unfreeze the sleep process. We expect the
36 The sleep process is frozen. We then thaw the process before it exits.
[all …]
|
| /third_party/unity/docs/ |
| D | ThrowTheSwitchCodingStandard.md | 6 followed. We're not perfect. Please be polite where you notice these discrepancies
14 Being consistent makes code easier to understand. We've tried to keep
22 vision for these tools. We're C developers and embedded software developers.
45 default. We believe that if you're working with a simple compiler and target,
52 Let's talk about naming things. Programming is all about naming things. We name
67 We want to read our code. This means we like names and flow that are more
68 naturally read. We try to avoid double negatives. We try to avoid cryptic
74 We like descriptive names for things, especially functions and variables.
77 longer than the average. Guilty. We're okay with a bit more typing if it
89 naming. We find i, j, and k are better loop counters than loopCounterVar or
[all …]
|
| /third_party/cJSON/tests/unity/docs/ |
| D | ThrowTheSwitchCodingStandard.md | 6 followed. We're not perfect. Please be polite where you notice these discrepancies
14 Being consistent makes code easier to understand. We've made an attempt to keep
22 vision for these tools. We're C developers and embedded software developers.
45 default. We believe that if you're working with a simple compiler and target,
52 Let's talk about naming things. Programming is all about naming things. We name
67 We want to read our code. This means we like names and flow that are more
68 naturally read. We try to avoid double negatives. We try to avoid cryptic
74 We like descriptive names for things, especially functions and variables.
77 longer than the average. Guilty. We're okay with a tiny bit more typing if it
90 naming. We find i, j, and k are better loop counters than loopCounterVar or
[all …]
|
| /third_party/gstreamer/gstreamer/docs/random/wtay/ |
| D | abstract | 1 This paper will present the GStreamer Media framework. We
8 We then go into more detail about the different components of
14 We expand on the scheduler that is responsible for making sure all
16 data. We explain one of the possible scheduling methods using
22 types between plugins. We continue with an explanation of how
27 or seek and flush events. We explain how these events work and
30 We finally cover some of the interesting libraries that are
31 provided with GStreamer, such as the bytestream library. We
|
| /third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/lib/Target/SystemZ/ |
| D | README.txt | 5 The initial backend is deliberately restricted to z10. We should add support
35 We don't use the BRANCH ON INDEX instructions.
39 We only use MVC, XC and CLC for constant-length block operations.
40 We could extend them to variable-length operations too,
47 We don't use CUSE or the TRANSLATE family of instructions for string
52 We don't take full advantage of builtins like fabsl because the calling
66 We don't use ICM, STCM, or CLM.
70 We don't use ADD (LOGICAL) HIGH, SUBTRACT (LOGICAL) HIGH,
151 We might want to model all access registers and use them to spill
156 We might want to use the 'overflow' condition of eg. AR to support
|
| /third_party/flutter/skia/third_party/externals/angle2/doc/ |
| D | Update20120704.md | 3 We haven't posted an update on the development status of ANGLE in quite some
17 We have recently completed the implementation of depth texture support
28 We have also made a number of improvements in the shader compiler.
30 * We addressed a number of defects related to scoping differences between HLSL and
31 GLSL and improved the scoping support in ANGLE's compiler front-end. We also
34 * We addressed a number of correctness issues in the GLSL to HLSL
35 translation process. We fixed some bugs related to constant propagation and
41 * We implemented detection
63 explicitly defined. We use these new functions instead of the original ones in
71 current ES 2.0 implementations. We would only be able to achieve parity with
[all …]
|
| /third_party/skia/third_party/externals/angle2/doc/ |
| D | Update20120704.md | 3 We haven't posted an update on the development status of ANGLE in quite some
17 We have recently completed the implementation of depth texture support
28 We have also made a number of improvements in the shader compiler.
30 * We addressed a number of defects related to scoping differences between HLSL and
31 GLSL and improved the scoping support in ANGLE's compiler front-end. We also
34 * We addressed a number of correctness issues in the GLSL to HLSL
35 translation process. We fixed some bugs related to constant propagation and
41 * We implemented detection
63 explicitly defined. We use these new functions instead of the original ones in
71 current ES 2.0 implementations. We would only be able to achieve parity with
[all …]
|
| /third_party/flutter/engine/flutter/lib/web_ui/lib/src/engine/ |
| D | alarm_clock.dart | 55 // We use the "not before" logic instead of "is after" because zero-duration
66 // different from the current _datetime. We need to decide whether we need
69 // We didn't have an existing timer, so create a new one.
73 'We can only have a timer if there is a non-null datetime');
81 // We don't need to do anything in the "else" branch. If the new value
100 // We use the "not before" logic instead of "is after" because we may have
106 // The timer fired before the target date. We need to reschedule.
|
| /third_party/node/doc/guides/ |
| D | technical-values.md | 7 evolve. We hope they are useful to people new
27 We value ensuring that developers are productive and enjoy developing
49 We value keeping Node.js safe, performant, and lightweight.
50 We value enabling the ability to investigate and debug problems in
61 We value the productivity and happiness of the Node.js maintainers.
69 We value providing developers with modern APIs and technologies
|
| /third_party/nghttp2/doc/sources/ |
| D | security.rst | 17 We write the security advisory and get CVE number from GitHub
18 privately. We also discuss the disclosure date to the public.
20 We make a new release with the fix at the same time when the
28 mailing list. We also open a new issue on `nghttp2 issue tracker
35 Security advisory is disclosed on GitHub. We also post the
|
| /third_party/boost/libs/outcome/doc/src/content/tutorial/advanced/interop/ |
| D | app-map-httplib1.md | 8 failure handling mechanism. We cannot modify those third party library
11 We start by dealing with the HTTP library. We will integrate this
13 STL exception type. We then type erase it into an `exception_ptr`
|
| /third_party/curl/tests/data/ |
| D | test1097 | 15 HTTP/1.1 200 We are fine and cool
24 HTTP/1.1 200 We are fine and cool
30 HTTP/1.1 200 We are fine and cool
33 HTTP/1.1 200 We are fine and cool
|
| /third_party/pulseaudio/shell-completion/zsh/ |
| D | _pulseaudio | 290 # We're completing the first parameter after "list".
296 # We're completing the second parameter after "list". As
306 # We're completing the first parameter after "play-sample".
309 # We're completing the second parameter after "play-sample".
316 # We're completing the first parameter after "load-module".
319 # We're completing the second or later parameter after
327 # We're completing the first parameter after "move-sink-input".
333 # We're completing the second parameter after
341 # We're completing the first parameter after
347 # We're completing the second parameter after
[all …]
|
| /third_party/skia/third_party/externals/spirv-cross/shaders-msl/comp/ |
| D | cfg-preserve-parameter.comp | 3 // We write in all paths (and no reads), so should just be out.
12 // We write in all paths (and no reads), so should just be out.
27 // We don't write in all paths, so should be inout.
|
| /third_party/skia/third_party/externals/spirv-cross/shaders/comp/ |
| D | cfg-preserve-parameter.comp | 3 // We write in all paths (and no reads), so should just be out.
12 // We write in all paths (and no reads), so should just be out.
27 // We don't write in all paths, so should be inout.
|
| /third_party/boost/libs/python/doc/numpy/tutorial/ |
| D | dtype.rst | 19 Next, we create the shape and dtype. We use the get_builtin method to get the numpy dtype correspon…
31 We can also print the dtypes of the data members of the ndarray by using the get_dtype method for t…
35 We can also create custom dtypes and build ndarrays with the custom dtypes
37 We use the dtype constructor to create a custom dtype. This constructor takes a list as an argument.
51 We are now ready to create an ndarray with dimensions specified by \*shape\* and of custom dtpye ::
|
| /third_party/boost/libs/python/doc/html/numpy/_sources/tutorial/ |
| D | dtype.rst.txt | 19 Next, we create the shape and dtype. We use the get_builtin method to get the numpy dtype correspon…
31 We can also print the dtypes of the data members of the ndarray by using the get_dtype method for t…
35 We can also create custom dtypes and build ndarrays with the custom dtypes
37 We use the dtype constructor to create a custom dtype. This constructor takes a list as an argument.
51 We are now ready to create an ndarray with dimensions specified by \*shape\* and of custom dtpye ::
|
| /third_party/libjpeg-turbo/ |
| D | example.txt | 11 * We present these routines in the same coding style used in the JPEG code
54 * We present a minimal version that does not worry about refinements such
81 * Sample routine for JPEG compression. We assume that the target file name
91 * compression/decompression processes, in existence at once. We refer
111 /* We have to set up the error handler first, in case the initialization
198 * which is the number of scanlines actually written. We could get away
233 * buffer, but to send it line-by-line someplace else. We need a one-
253 * We use C's setjmp/longjmp facility to return control. This means that the
255 * establish the return point. We want the replacement error_exit to do a
283 /* We could postpone this until after returning, if we chose. */
[all …]
|
| /third_party/grpc/src/python/grpcio/grpc/_cython/_cygrpc/ |
| D | grpc.pxi | 40 # We don't care about the internals
104 # We don't care about the internals.
164 # We don't care about the internals (and in fact don't know them)
168 # We don't care about the internals (and in fact don't know them)
172 # We don't care about the internals (and in fact don't know them)
176 # We don't care about the internals (and in fact don't know them)
460 # We don't care about the internals
464 # We don't care about the internals
495 # We don't care about the internals (and in fact don't know them)
499 # We don't care about the internals (and in fact don't know them)
[all …]
|
| /third_party/curl/docs/ |
| D | CODE_STYLE.md | 19 We also work hard on writing code that are warning-free on all the major
29 functions should be made static. We like lower case names.
36 We use only spaces for indentation, never TABs. We use two spaces for each new
50 introduced in the C standard until C99. We use only **/* comments */**.
140 assigning variables within if/while conditions. We frown upon this style:
157 We never write multiple statements on the same source line, even for very
198 We use the 'return' statement without extra parentheses around the value:
265 Use **#ifdef HAVE_FEATURE** to do conditional code. We avoid checking for
270 We also encourage use of macros/functions that possibly are empty or defined
|
| /third_party/boost/libs/outcome/doc/src/content/tutorial/advanced/hooks/ |
| D | keeping_state.md | 9 We could take the easier route and simply store it into an allocated block and
14 We therefore are going to need some completely static and trivially typed storage
19 The extended error info is kept in a sixteen item long, thread local, ring buffer. We continuously
|
| /third_party/flutter/skia/third_party/externals/libjpeg-turbo/ |
| D | example.txt | 11 * We present these routines in the same coding style used in the JPEG code
54 * We present a minimal version that does not worry about refinements such
81 * Sample routine for JPEG compression. We assume that the target file name
91 * compression/decompression processes, in existence at once. We refer
111 /* We have to set up the error handler first, in case the initialization
198 * which is the number of scanlines actually written. We could get away
233 * buffer, but to send it line-by-line someplace else. We need a one-
253 * We use C's setjmp/longjmp facility to return control. This means that the
255 * establish the return point. We want the replacement error_exit to do a
283 /* We could postpone this until after returning, if we chose. */
[all …]
|
| /third_party/boost/libs/geometry/doc/ |
| D | quickstart.qbk | 41 under the name `within`. We show its usage here checking a __boost_tuple__ (as a point)
48 We can calculate the area of a polygon:
52 We calculate distance again, now using a C array point and a __boost_tuple__ point:
76 We approximate the Earth as a sphere and calculate the distance between Amsterdam
86 in __boost_geometry__ we can use them. We can, for example, check if two
|
| D | design_rationale.qbk | 50 calculating the distance between other point types than just [*mypoint]. We add two template
69 We need to take a generic approach and allow any point type as input to the distance function.
107 It is too verbose for a function like this, used so often in the library. We can shorten the syntax
125 our distance function. We can use a `for` loop to walk through dimensions, but for loops have
196 We assumed double above. What if our points are in integer?
198 We can easily add a traits class, and we will do that. However, the distance between two integer
200 roots. We handle these cases below, in another paragraph. For the moment we keep returning double,
223 We now can modify our distance algorithm again. Because it still returns double, we only
227 should handle those strange cases. We have to choose one of the coordinate types and of course
229 and it is not related to geometry. We just assume that there is a meta-function `select_most_precis…
[all …]
|
| /third_party/boost/tools/build/notes/ |
| D | build_dir_option.txt | 9 We need a --build-dir option that users building from read-only
17 We can achieve the desired effect manually by adding something like this
24 We need to automate this, but essentially, --build-dir will only affect
44 We can't drop "bin.v2" because it's quite possible that the name of build dir
56 We'll emit a warning if Jamroot does not define project id, and --build-dir
|