Timeline for Using "iff" in documentation
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 20, 2024 at 20:19 | comment | added | Jasen | I'm guessing OP thought iff was saving words. in some languages there are more than two boolean values | |
| Nov 20, 2024 at 12:29 | comment | added | U. Windl | So "This function returns True iff the value of foo is larger than bar, if it returns at all, and if it returns a Boolean value" ;-) | |
| Nov 20, 2024 at 8:42 | comment | added | virolino | In your example, the problem is not the use of "iff", but the fact that there are no additional requirements about what-if-not-iff ... So if one extreme is bad, the other extreme is not inherently good either. Just to clarify: "This function returns True if-and-only-if the value of foo is larger than bar." is equally bad from the point-of-view of "perhaps the function sometime does not return, or sometimes returns a value that is neither true nor false". | |
| Nov 19, 2024 at 6:45 | history | answered | Jasen | CC BY-SA 4.0 |