| ... |
... |
@@ -1,3 +1,39 @@ |
| 1 |
1 |
The explanations given here do not claim to be complete. They merely serve as a brief description to give an idea of the respective term. For more detailed information, the Internet should be consulted. Note that some of these technical terms are fuzzy, overlap with other terms, or have different meanings depending on the context or the people using them. This Glossary is an attempt to structure these terms in a concise manner. Be open to variations as you talk and work with other developers. |
| 2 |
2 |
|
|
3 |
+| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | |
|
4 |
+| **Term** | **Explanation** | |
|
5 |
+| Abstraction | |
|
6 |
+ |
|
7 |
+1) The counterpart to 'Concretion', refers to interfaces and abstract classes that define behavior (function signatures) but leave the internal operacommand-line interfacestion of these functions undefined. |
|
8 |
+ |
|
9 |
+2) A higher-level, generalized unit of code. Duplication across multiple functions can be resolved by creating an 'abstraction' - a separate function containing the shared code. This adheres to the DRY principle. | |
|
10 |
+| | | |
|
11 |
+| | | |
|
12 |
+| | | |
|
13 |
+| | | |
|
14 |
+| | | |
|
15 |
+| | | |
|
16 |
+| | | |
|
17 |
+| | | |
|
18 |
+| | | |
|
19 |
+| | | |
|
20 |
+| | | |
|
21 |
+| | | |
|
22 |
+| | | |
|
23 |
+| | | |
|
24 |
+| | | |
|
25 |
+| | | |
|
26 |
+| | | |
|
27 |
+| | | |
|
28 |
+| | | |
|
29 |
+| | | |
|
30 |
+| | | |
|
31 |
+| | | |
|
32 |
+| | | |
|
33 |
+| | | |
|
34 |
+| | | |
|
35 |
+| | | |
|
36 |
+| | | |
|
37 |
+| | | |
|
38 |
+ |
| 3 |
3 |
|
