Timeline for Where should the logic concerning a class's behavior reside? In the class itself or in the calling subroutine?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 24, 2019 at 14:08 | vote | accept | PBeezy | ||
| Jan 24, 2019 at 4:19 | comment | added | John Douma | Please don't say "if (booleanExpression == false)". | |
| Jan 24, 2019 at 1:46 | answer | added | Karæthon | timeline score: 2 | |
| Jan 24, 2019 at 0:04 | comment | added | Erik Eidt | (a) Make your abstractions simple for the calling clients to use -- as in your #2. (b) if there are multiple calling clients it will be more DRY to put such logic inside the encapsulation than to expect each of the calling clients to perform this logic. (c) if you generalize to other vehicle types, it is possible that some won't need "starting". | |
| Jan 23, 2019 at 23:03 | answer | added | Tangurena | timeline score: 6 | |
| Jan 23, 2019 at 22:45 | review | First posts | |||
| Jan 24, 2019 at 14:19 | |||||
| Jan 23, 2019 at 22:43 | history | asked | PBeezy | CC BY-SA 4.0 |