| /external/snakeyaml/src/test/java/examples/collections/ |
| D | TypeSafeMapTest.java | 27 * Test MapBean->Map<String, Developer> developers <br/>
38 Map<String, Developer2> developers = new LinkedHashMap<String, Developer2>(); in testDumpMap() local
39 developers.put("team1", new Developer2("Fred", "creator")); in testDumpMap()
40 developers.put("team2", new Developer2("John", "committer")); in testDumpMap()
41 bean.setDevelopers(developers); in testDumpMap()
55 Map<String, Developer2> developers = new LinkedHashMap<String, Developer2>(); in testDumpMap2() local
56 developers.put("team1", new Developer2("Fred", "creator")); in testDumpMap2()
57 developers.put("team2", new Developer2("John", "committer")); in testDumpMap2()
58 developers.put("team3", new Developer222("Bill", "head")); in testDumpMap2()
59 bean.setDevelopers(developers); in testDumpMap2()
[all …]
|
| D | TypeSafeMap2Test.java | 28 * Test MapBean->Map<Enum, Developer> developers <br/>
38 Map<Color, Developer2> developers = new LinkedHashMap<Color, Developer2>(); in testDumpMap() local
39 developers.put(Color.WHITE, new Developer2("Fred", "creator")); in testDumpMap()
40 developers.put(Color.BLACK, new Developer2("John", "committer")); in testDumpMap()
41 bean.setDevelopers(developers); in testDumpMap()
56 Map<Color, Developer2> developers = new LinkedHashMap<Color, Developer2>(); in testMap2() local
57 developers.put(Color.WHITE, new Developer2("Fred", "creator")); in testMap2()
58 developers.put(Color.RED, new SuperMan("Jason", "contributor", true)); in testMap2()
59 developers.put(Color.BLACK, new Developer2("John", "committer")); in testMap2()
60 bean.setDevelopers(developers); in testMap2()
[all …]
|
| D | TypeSafeListWithInterfaceTest.java | 27 * Test ListBean->List<Human> developers <br/>
37 List<Human> developers = new ArrayList<Human>(); in testDumpList() local
38 developers.add(new Developer("Fred", "creator")); in testDumpList()
39 developers.add(new Committer("John", "committer", 34)); in testDumpList()
40 bean.setDevelopers(developers); in testDumpList()
56 … assertTrue(e.getMessage(), e.getMessage().contains("Cannot create property=developers")); in testLoadWrongList()
70 List<Human> developers = parsed.getDevelopers(); in testLoadList() local
71 assertEquals(2, developers.size()); in testLoadList()
72 … assertEquals("Developer must be recognised.", Developer.class, developers.get(0).getClass()); in testLoadList()
73 Developer fred = (Developer) developers.get(0); in testLoadList()
[all …]
|
| D | TypeSafeListTest.java | 27 * Test ListBean->List<Developer> developers <br/>
37 List<Developer> developers = new ArrayList<Developer>(); in testDumpList() local
38 developers.add(new Developer("Fred", "creator")); in testDumpList()
39 developers.add(new Developer("John", "committer")); in testDumpList()
40 bean.setDevelopers(developers); in testDumpList()
58 List<Developer> developers = parsed.getDevelopers(); in testLoadList() local
59 assertEquals(2, developers.size()); in testLoadList()
60 … assertEquals("Developer must be recognised.", Developer.class, developers.get(0).getClass()); in testLoadList()
61 Developer fred = developers.get(0); in testLoadList()
69 private List<Developer> developers; field in TypeSafeListTest.ListBean1
[all …]
|
| D | TypeSafeSetImplementationsTest.java | 40 SortedSet<Developer> developers = new TreeSet<Developer>(); in testDumpSet() local
41 developers.add(new Developer("John", "founder")); in testDumpSet()
42 developers.add(new Developer("Karl", "user")); in testDumpSet()
43 bean.setDevelopers(developers); in testDumpSet()
58 SortedSet<Developer> developers = new TreeSet<Developer>(); in testDumpSet2() local
59 developers.add(new Developer("John", "founder")); in testDumpSet2()
60 developers.add(new Developer("Karl", "user")); in testDumpSet2()
61 developers.add(new SuperDeveloper("Bill", "super")); in testDumpSet2()
62 bean.setDevelopers(developers); in testDumpSet2()
84 SortedSet<Developer> developers = parsed.getDevelopers(); in testLoadSet() local
[all …]
|
| D | TypeSafeListNoGerericsTest.java | 28 * Test ListBean->List developers <br/>
38 List<Developer> developers = new ArrayList<Developer>(); in testDumpList() local
39 developers.add(new Developer("Fred", "creator")); in testDumpList()
40 developers.add(new Developer("John", "committer")); in testDumpList()
41 bean.setDevelopers(developers); in testDumpList()
60 List<Map<String, String>> developers = parsed.getDevelopers(); in testLoadList() local
61 assertEquals(2, developers.size()); in testLoadList()
62 Map<String, String> fred = developers.get(0); in testLoadList()
71 private List developers; field in TypeSafeListNoGerericsTest.ListBean
94 return developers; in getDevelopers()
[all …]
|
| D | TypeSafePriorityTest.java | 28 * Test ListBean->List<Human> developers <br/>
41 descr.putListPropertyType("developers", Developer.class); in testLoadList2()
45 List<Human> developers = parsed.getDevelopers(); in testLoadList2() local
46 assertEquals(2, developers.size()); in testLoadList2()
47 … assertEquals("Committer must be recognised.", Developer.class, developers.get(0).getClass()); in testLoadList2()
48 Developer fred = (Developer) developers.get(0); in testLoadList2()
51 Developer john = (Developer) developers.get(1); in testLoadList2()
58 private List<Human> developers; field in TypeSafePriorityTest.ListBean
73 return developers; in getDevelopers()
76 public void setDevelopers(List<Human> developers) { in setDevelopers() argument
[all …]
|
| D | ListFileldBeanTest.java | 27 * Test public field ListBean->List<Developer> developers <br/>
37 List<Developer> developers = new ArrayList<Developer>(); in testDumpList() local
38 developers.add(new Developer("Fred", "creator")); in testDumpList()
39 developers.add(new Developer("John", "committer")); in testDumpList()
40 bean.developers = developers; in testDumpList()
59 List<Developer> developers = parsed.developers; in testLoadList() local
60 assertEquals(2, developers.size()); in testLoadList()
61 … assertEquals("Developer must be recognised.", Developer.class, developers.get(0).getClass()); in testLoadList()
62 Developer fred = developers.get(0); in testLoadList()
70 public List<Developer> developers; field in ListFileldBeanTest.ListFieldBean
|
| /external/clang/docs/ |
| D | ClangTools.rst | 6 designed for use by C++ developers who are already using and enjoying
13 side-project so that developers who don't want or need to build them
32 document is currently focused on Clang and Clang Tool developers, not on
39 used by C++ developers. That is they are *not* primarily for use by
40 Clang developers, although they are hopefully useful to C++ developers
102 and features of the tools for other tool developers; each tool should
150 comments with deduced types. The motivation is that there are developers
|
| /external/mesa3d/docs/ |
| D | developers.html | 5 <title>Developers</title>
17 <h1>Developers</h1>
20 Both professional and volunteer developers contribute to Mesa.
24 employs several of the main Mesa developers including Brian Paul
|
| /external/python/cpython2/Doc/distributing/ |
| D | index.rst | 12 available for other Python developers to use under open source license terms.
39 developers and documentation authors responsible for the maintenance and
71 This means that other developers require explicit permission to copy, use,
75 relatively consistent way, allowing developers to share and collaborate
77 This leaves many developers free to spend more time focusing on the problems
81 reasonably straightforward for developers to make their own contributions
|
| /external/llvm/docs/ |
| D | index.rst | 167 For developers of applications which use LLVM as a library.
232 For API clients and LLVM developers.
398 The LLVM project's policy towards developers and their contributions.
411 This is a guide to preparing LLVM releases. Most developers can ignore it.
414 …This is a guide to validate a new release, during the release process. Most developers can ignore …
426 LLVM has a thriving community of friendly and helpful developers.
444 This list contains all commit messages that are made when LLVM developers
474 Users and developers of the LLVM project (including subprojects such as Clang)
|
| D | DeveloperPolicy.rst | 12 policy towards developers and their contributions. The intent of this policy is
21 #. Attract both users and developers to the LLVM project.
39 This section contains policies that pertain to frequent LLVM developers. We
49 Developers should stay informed by reading at least the "dev" mailing list for
64 We recommend that active developers register an email account with `LLVM
131 #. All developers are required to have significant changes reviewed before they
157 asking for valuable time from other professional developers.
158 * Ask for help on IRC. Developers on IRC will be able to either help you
164 Developers should participate in code reviews as both reviewers and
208 Developers are required to create test cases for any bugs fixed and any new
[all …]
|
| /external/libyuv/files/docs/ |
| D | deprecated_builds.md | 7 You'll need to have depot tools installed: https://www.chromium.org/developers/how-tos/install-depo…
106 http://www.chromium.org/developers/how-tos/build-instructions-ios
233 If you get a compile error for atlthunk.lib on Windows, read http://www.chromium.org/developers/how…
297 If you get a compile error for atlthunk.lib on Windows, read http://www.chromium.org/developers/how…
357 See Chromium instructions for sanitizers: https://www.chromium.org/developers/testing/undefinedbeha…
389 For more information, see http://www.chromium.org/developers/how-tos/using-valgrind
397 For more info, see http://www.chromium.org/developers/how-tos/using-valgrind/threadsanitizer
405 For more info, see http://dev.chromium.org/developers/testing/addresssanitizer
|
| /external/python/cpython2/Doc/distutils/ |
| D | introduction.rst | 18 Using the Distutils is quite simple, both for module developers and for
33 Not all module developers have access to a multitude of platforms, so it's not
37 developers, build them on one or more platforms, and release the resulting built
107 First, both developers and installers have the same basic user interface, i.e.
109 :command:`sdist` command is almost exclusively for module developers, while
110 :command:`install` is more often for installers (although most developers will
|
| /external/protobuf/ |
| D | README.md | 8 https://developers.google.com/protocol-buffers/
15 can find [protobuf's documentation on the Google Developers site](https://developers.google.com/pro…
77 https://developers.google.com/protocol-buffers/
|
| /external/protobuf/util/ |
| D | README.md | 8 https://developers.google.com/protocol-buffers/
15 can find [protobuf's documentation on the Google Developers site](https://developers.google.com/pro…
77 https://developers.google.com/protocol-buffers/
|
| /external/lzma/Java/Tukaani/maven/ |
| D | pom_template.xml | 39 <developers>
44 </developers>
49 as <developers> that should be contacted if someone wants
|
| /external/sfntly/ |
| D | README.md | 7 …that allows software developers to build tools that manipulate fonts in ways that haven't been eas…
11 …ellaneous tables. This level of support provides for many of the needs developers have related to …
|
| /external/valgrind/docs/internals/ |
| D | why-no-libc.txt | 4 Cc: valgrind-developers@lists.sourceforge.net
5 Subject: Re: [Valgrind-developers] Using standard C library in valgrind tool
54 the glibc and Valgrind developers don't consider them bugs, and so
|
| /external/syslinux/core/lwip/ |
| D | README | 38 and developers using the stack often submit bug fixes, improvements,
44 mailing list. A core team of developers will commit changes to the
51 developers.
|
| /external/drrickorang/LoopbackApp/ |
| D | CONTRIBUTORS | 6 # https://developers.google.com/open-source/cla/individual
7 # https://developers.google.com/open-source/cla/corporate
|
| /external/walt/ |
| D | CONTRIBUTORS | 6 # https://developers.google.com/open-source/cla/individual
7 # https://developers.google.com/open-source/cla/corporate
|
| /external/lisa/ |
| D | README.md | 3 *developers, contributors and testers.*
11 kernel developers to measure the impact of modifications in core parts
57 * **enables** kernel developers to easily post process data to produce
|
| /external/bart/ |
| D | README.md | 11 developers as well as automating the testing of "difficult to test" behaviours.
13 #### Kernel Developers
59 # For developers
|