Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
Mathematically, the purpose of a function is to return an output. However, in a programming context functions often have side effects. It is even common to call functions for the side effects alone...
#2: Post edited
by
matthewsnyder
·
2023-08-09T20:42:07Z (9 months ago)
- Mathematically, the purpose of a function is to return an output. However, in a programming context functions often have *side effects*. It is even common to call functions *for the side effects alone*. The classic example is `print(x)`, which has a useful side effect and no output.
- It seems to me that we can taxonomize functions into five classes based on human expectations about their outputs and side effects:
- 1. Functions with no side effects, where the output is most interesting
- 2. Functions with side effects, but the output is most interesting
- 3. Functions with an output, but the side effect is more interesting than the output
- * Example: `request(url, type="POST")` - the output is only a detail if we care to check whether the request succeeded, which may even be irrelevant in some cases
- 4. Functions with no output, executed for their side effects
- 5. Functions with no output or side effect to speak of (usually created for testing or as placeholders)
- Is there a terminology for these classes?
- Mathematically, the purpose of a function is to return an output. However, in a programming context functions often have *side effects*. It is even common to call functions *for the side effects alone*. The classic example is `print(x)`, which has a useful side effect and no output.
- It seems to me that we can taxonomize functions into five classes based on human expectations about their outputs and side effects:
- 1. Functions with no side effects, where the output is most interesting
- 2. Functions with side effects, but the output is most interesting
- * Technically, all functions are like this, because running things on the computer always has side effects like using up CPU and RAM.
- 3. Functions with an output, but the side effect is more interesting than the output
- * Example: `request(url, type="POST")` - the output is only a detail if we care to check whether the request succeeded, which may even be irrelevant in some cases
- 4. Functions with no output, executed for their side effects
- 5. Functions with no output or side effect to speak of (usually created for testing or as placeholders)
- Is there a terminology for these classes?
#1: Initial revision
by
matthewsnyder
·
2023-08-09T20:40:46Z (9 months ago)
Terms for types of functions with respect to side effects
Mathematically, the purpose of a function is to return an output. However, in a programming context functions often have *side effects*. It is even common to call functions *for the side effects alone*. The classic example is `print(x)`, which has a useful side effect and no output.
It seems to me that we can taxonomize functions into five classes based on human expectations about their outputs and side effects:
1. Functions with no side effects, where the output is most interesting
2. Functions with side effects, but the output is most interesting
3. Functions with an output, but the side effect is more interesting than the output
* Example: `request(url, type="POST")` - the output is only a detail if we care to check whether the request succeeded, which may even be irrelevant in some cases
4. Functions with no output, executed for their side effects
5. Functions with no output or side effect to speak of (usually created for testing or as placeholders)
Is there a terminology for these classes?