| ... |
... |
@@ -10,7 +10,7 @@ |
| 10 |
10 |
* events: one input, no output, reader should recognize that it is about an event by the functions context and name→ Otherwise, rather not use monadic functions. |
| 11 |
11 |
* Avoid flag arguments. It shows that the function performs two tasks, depending on whether the flag is true or false. |
| 12 |
12 |
* Dyads should be converted to monads if possible, but cannot always be avoided. Sometimes they are also useful, e.g. when passing 2D coordinates, because the arguments are connected by a cohesion. |
| 13 |
|
-* Argument objects: If many arguments are to be passed to a function, it often makes sense to combine them as a separate concept in a new class/data structure. |
|
13 |
+* Argument objects: If many arguments are to be passed to a function, it often makes sense to combine them as a separate concept in a new class. |
| 14 |
14 |
* Verbs and keywords: Function names can form a logical combination with the arguments, such as "write(name)", or you can integrate the arguments into the function name, e.g. to avoid interchanges. |
| 15 |
15 |
|
| 16 |
16 |
#### **One Task Per Function** |
