/external/pdfium/testing/resources/javascript/ |
D | globals_expected.txt | 3 Alert: setPersistent = function setPersistent() { [native code] }, own property = true 15 Alert: setPersistent = function setPersistent() { [native code] }, own property = true 16 Alert: true_var = true, own property = true 17 Alert: false_var = false, own property = true 18 Alert: zero_var = 0, own property = true 19 Alert: number_var = -3.918, own property = true 20 Alert: string_var = This is a string, own property = true 21 Alert: object_var = [object Object], own property = true 22 Alert: null_var = null, own property = true 23 Alert: undefined_var = undefined, own property = true [all …]
|
/external/toybox/toys/posix/ |
D | chgrp.c | 77 char **s, *own; in chgrp_main() local 85 own = xstrdup(*toys.optargs); in chgrp_main() 86 if ((grp = strchr(own, ':')) || (grp = strchr(own, '.'))) { in chgrp_main() 90 if (*own) TT.owner = xgetuid(TT.owner_name = own); in chgrp_main() 100 if (CFG_TOYBOX_FREE && ischown) free(own); in chgrp_main()
|
/external/wpa_supplicant_8/wpa_supplicant/dbus/ |
D | dbus-wpa_supplicant.conf | 6 <allow own="fi.epitest.hostap.WPASupplicant"/> 11 <allow own="fi.w1.wpa_supplicant1"/> 18 <deny own="fi.epitest.hostap.WPASupplicant"/> 21 <deny own="fi.w1.wpa_supplicant1"/>
|
/external/dhcpcd-6.8.2/dbus/ |
D | dhcpcd-dbus.conf | 4 <!-- Both root and dhcp can own the dhcpcd service --> 6 <allow own="org.chromium.dhcpcd"/> 11 <allow own="org.chromium.dhcpcd"/>
|
/external/stressapptest/src/ |
D | findmask.inc | 1 // This is the body of a uintptr_t array definition. Fill in your own addresses. 3 0x38d3c5ad, // replace with your own
|
/external/selinux/dbus/ |
D | org.selinux.conf | 8 <!-- Only root can own the service --> 10 <allow own="org.selinux"/>
|
/external/v8/testing/gmock/ |
D | CMakeLists.txt | 12 option(gmock_build_tests "Build all of Google Mock's own tests." OFF) 49 # directory in a subdirectory of our own as VC compilation may break 69 # <= VS 2010 <= 10 <= 1600 Use Google Tests's own tuple. 97 # Google Mock's own tests. 149 # conflict with our own definitions. Therefore using our own tuple does not
|
/external/googletest/googlemock/ |
D | CMakeLists.txt | 12 option(gmock_build_tests "Build all of Google Mock's own tests." OFF) 49 # directory in a subdirectory of our own as VC compilation may break 69 # <= VS 2010 <= 10 <= 1600 Use Google Tests's own tuple. 113 # Google Mock's own tests. 165 # conflict with our own definitions. Therefore using our own tuple does not
|
/external/llvm/test/MC/Disassembler/X86/ |
D | prefixes.txt | 68 # Test that a prefix on it's own works. It's debatable as to if this is 69 # something that is considered valid, but however as LLVM's own disassembler 71 # should be capable of re-consuming it's own output.
|
/external/python/cpython2/Lib/email/test/data/ |
D | msg_44.txt | 23 to reflect upon our own 30 to reflect upon our own
|
D | msg_04.txt | 25 to reflect upon our own 34 to reflect upon our own
|
/external/webrtc/webrtc/ |
D | supplement.gypi | 40 # Replace Chromium's LSan suppressions with our own for WebRTC. 49 # Replace Chromium's TSan v2 suppressions with our own for WebRTC.
|
/external/ltp/testcases/kernel/security/prot_hsymlinks/ |
D | README | 19 1. Users who own sticky world-writable directory can't follow symlinks 20 inside that directory if their don't own ones. All other users can follow.
|
/external/webrtc/webrtc/modules/desktop_capture/win/ |
D | desktop.cc | 19 Desktop::Desktop(HDESK desktop, bool own) : desktop_(desktop), own_(own) { in Desktop() argument
|
/external/libcxx/lib/abi/ |
D | CHANGELOG.TXT | 24 must contain its own definition. 91 must contain its own definition. 107 functions will contain their own definition. 179 must contain its own definition.
|
/external/clang/test/SemaObjC/ |
D | warn-deprecated-implementations.m | 18 + (void)F { } // No warning, implementing its own deprecated method 28 - (void) G {} // No warning, implementing its own deprecated method
|
/external/antlr/antlr-3.4/runtime/C/doxygen/ |
D | buildrec.dox | 58 /// // You may adopt your own practices by all means, but in general it is best 61 /// // multiple times) and your own project related header files. Use <> to include and 97 /// // You can create your own input stream type (copy one of the existing ones) and override a… 98 /// // individual function by installing your own pointer after you have created the standard 112 /// // supplied to the generated parser, and you can write your own token stream and pass this … 133 /// // out the nodes upon request. You can make your own tree types and adaptors 192 /// // Note tha even if you implement your own token structure, it will always 195 /// // it that should point to your own outer token structure. 237 /// // keeping your own flags as part of the error trapping, but here is how you can
|
D | doxygengroups.dox | 15 /// your own function. Some of these methods create other 'objects' (instances of 16 /// typedef structures), which allows you install your own method and create your 17 /// own implementation of these. 31 /// then override any part of the implementation by installing your own 36 /// your own. In your grammar, you would place the following 49 /// install your own implementations of the #ANTLR3_BASE_RECOGNIZER interface
|
/external/v8/testing/gtest/ |
D | CMakeLists.txt | 19 option(gtest_build_tests "Build all of gtest's own tests." OFF) 65 # <= VS 2010 <= 10 <= 1600 Use Google Tests's own tuple. 107 # Google Test's own tests. 186 # conflict with our own definitions. Therefore using our own tuple does not
|
/external/pdfium/build_overrides/ |
D | README.md | 6 For example: V8 can be built on its own (in a "standalone" configuration), 15 create its own build_overrides/v8.gni file, and in it set
|
/external/protobuf/gtest/ |
D | README | 63 build Google Test and its own tests from an SVN checkout (described 141 Test's own tests. Instead, it just builds the Google Test library and 142 a sample test. You can use it as a starting point for your own build 238 enough for its own need, and will automatically use this when the 250 you want to force Google Test to use its own tuple library, just add 281 script, this is taken care of for you. If you use your own build 340 You may need to explicitly enable or disable Google Test's own TR1 347 supportted. You are encouraged to migrate to your own build system or 364 This section discusses how to make your own changes to Google Test. 369 functionality, you'll want to compile and run Google Test's own tests. [all …]
|
/external/google-breakpad/src/testing/gtest/ |
D | README | 63 build Google Test and its own tests from an SVN checkout (described 141 Test's own tests. Instead, it just builds the Google Test library and 142 a sample test. You can use it as a starting point for your own build 248 enough for its own need, and will automatically use this when the 260 you want to force Google Test to use its own tuple library, just add 291 script, this is taken care of for you. If you use your own build 358 You may need to explicitly enable or disable Google Test's own TR1 365 supportted. You are encouraged to migrate to your own build system or 382 This section discusses how to make your own changes to Google Test. 387 functionality, you'll want to compile and run Google Test's own tests. [all …]
|
/external/googletest/googletest/docs/ |
D | XcodeGuide.md | 27 …u are working with Subversion in your own code base, you can add Google Test as an external depend… 42 The next step is to build and add the gtest.framework to your own project. This guide describes two… 44 …* **Option 1** --- The simplest way to add Google Test to your own project, is to open gtest.xcode… 45 …ll need to add the gtest.xcodeproj file, not the framework itself, to your own Xcode project. Then… 54 …tories with Google Test, you'll have to copy the gtest.framework into your own build products dire…
|
D | V1_5_XcodeGuide.md | 27 …u are working with Subversion in your own code base, you can add Google Test as an external depend… 42 The next step is to build and add the gtest.framework to your own project. This guide describes two… 44 …* **Option 1** --- The simplest way to add Google Test to your own project, is to open gtest.xcode… 45 …ll need to add the gtest.xcodeproj file, not the framework itself, to your own Xcode project. Then… 54 …tories with Google Test, you'll have to copy the gtest.framework into your own build products dire…
|
D | V1_6_XcodeGuide.md | 27 …u are working with Subversion in your own code base, you can add Google Test as an external depend… 42 The next step is to build and add the gtest.framework to your own project. This guide describes two… 44 …* **Option 1** --- The simplest way to add Google Test to your own project, is to open gtest.xcode… 45 …ll need to add the gtest.xcodeproj file, not the framework itself, to your own Xcode project. Then… 54 …tories with Google Test, you'll have to copy the gtest.framework into your own build products dire…
|