/external/chromium_org/ppapi/utility/ |
README.txt | 2 features on top of the C++ wrappers. Using these classes is optional.
|
/external/chromium_org/third_party/WebKit/ManualTests/inspector-wrappers/ |
console-eval.html | 3 <script src="inspector-wrappers-test-utils.js"></script>
|
console-str-getter.html | 3 <script src="inspector-wrappers-test-utils.js"></script>
|
inspector-evaluate.html | 3 <script src="inspector-wrappers-test-utils.js"></script>
|
console-alert-document-body.html | 3 <script src="inspector-wrappers-test-utils.js"></script>
|
console-alert-object.html | 3 <script src="inspector-wrappers-test-utils.js"></script>
|
console-alert-this.html | 3 <script src="inspector-wrappers-test-utils.js"></script>
|
console-str-alert-object.html | 3 <script src="inspector-wrappers-test-utils.js"></script>
|
inspector-treeElementIdentifier.html | 3 <script src="inspector-wrappers-test-utils.js"></script>
|
inspector-hasAttributes.html | 3 <script src="inspector-wrappers-test-utils.js"></script>
|
/external/valgrind/main/docs/internals/ |
m_syswrap.txt | 7 POST wrappers for syscalls. It is important to observe these, else 12 and a great deal of commentary. The wrappers themselves live in
|
m_replacemalloc.txt | 9 And yet it must call the tool's malloc wrappers. How does it know where 18 the core the names of its malloc wrappers. These are stored in 22 GET_MALLOCFUNCS client request to get the names of the malloc wrappers
|
/external/wpa_supplicant_8/src/drivers/ |
rfkill.h | 2 * Linux rfkill helper functions for driver wrappers
|
netlink.h | 2 * Netlink helper functions for driver wrappers
|
/external/chromium_org/third_party/WebKit/Source/core/svg/properties/ |
SVGAnimatedListPropertyTearOff.h | 105 // Switch to new passed in value type & new wrappers list. The new wrappers list must be created for the new value. 111 ASSERT(animVal->values().size() == animVal->wrappers().size()); 112 ASSERT(animVal->wrappers().size() == m_animatedWrappers.size()); 124 ASSERT(animVal->values().size() == animVal->wrappers().size()); 125 ASSERT(animVal->wrappers().size() == m_animatedWrappers.size()); 128 ASSERT(animVal->values().size() == animVal->wrappers().size()); 129 ASSERT(animVal->wrappers().size() == m_wrappers.size()); 139 // Also existing wrappers which point directly at elements in the existing SVGLengthList have to be detached (so a copy 145 ASSERT(animVal->values().size() == animVal->wrappers().size()) [all...] |
SVGTransformListPropertyTearOff.h | 36 static PassRefPtr<SVGListPropertyTearOff<SVGTransformList> > create(AnimatedListPropertyTearOff* animatedProperty, SVGPropertyRole role, SVGTransformList& values, ListWrapperCache& wrappers) 39 return adoptRef(new SVGTransformListPropertyTearOff(animatedProperty, role, values, wrappers)); 74 SVGTransformListPropertyTearOff(AnimatedListPropertyTearOff* animatedProperty, SVGPropertyRole role, SVGTransformList& values, ListWrapperCache& wrappers) 75 : SVGListPropertyTearOff<SVGTransformList>(animatedProperty, role, values, wrappers)
|
/external/chromium/crypto/ |
mac_security_services_lock.h | 16 // The Mac OS X certificate and key management wrappers over CSSM are not
|
/external/chromium_org/crypto/ |
mac_security_services_lock.h | 16 // The Mac OS X certificate and key management wrappers over CSSM are not
|
/prebuilts/python/darwin-x86/2.7.5/lib/python2.7/wsgiref/ |
__init__.py | 5 * util -- Miscellaneous useful functions and wrappers
|
/prebuilts/python/linux-x86/2.7.5/lib/python2.7/wsgiref/ |
__init__.py | 5 * util -- Miscellaneous useful functions and wrappers
|
/external/bison/lib/ |
msvc-nothrow.h | 0 /* Wrappers that don't throw invalid parameter notifications 25 This file defines wrappers that turn such an invalid parameter notification
|
/external/chromium_org/win8/metro_driver/ |
stdafx.h | 11 #include <wrl\wrappers\corewrappers.h> 28 namespace mswrw = Microsoft::WRL::Wrappers;
|
/external/valgrind/main/ |
README_MISSING_SYSCALL_OR_IOCTL | 2 Dealing with missing system call or ioctl wrappers in Valgrind 7 ioctl wrappers you need, so that you can continue your debugging. If 18 What are syscall/ioctl wrappers? What do they do? 28 Syscall and ioctl wrappers have two jobs: 103 Writing your own syscall wrappers (see below for ioctl wrappers) 126 3. Add a case to the already-huge collection of wrappers in 148 If you find this difficult, read the wrappers for other syscalls 173 Writing your own ioctl wrappers 176 Is pretty much the same as writing syscall wrappers, except that al [all...] |
/external/guava/guava-tests/test/com/google/common/primitives/ |
PrimitivesTest.java | 65 Set<Class<?>> wrappers = Primitives.allWrapperTypes(); local 70 wrappers); local 73 wrappers.remove(Boolean.class);
|
/bootable/recovery/minadbd/ |
transport.h | 20 /* convenience wrappers around read/write that will retry on
|