Timeline for How should an abstract class require a value that will be constant for each subclass?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 30, 2021 at 19:08 | history | edited | Tulains Córdova | CC BY-SA 4.0 |
added 20 characters in body
|
| Jun 30, 2021 at 18:59 | vote | accept | cegredev | ||
| Jun 30, 2021 at 18:19 | comment | added | cegredev | That's probably what I'll do, thanks! | |
| Jun 30, 2021 at 18:01 | comment | added | Tulains Córdova | @Schred I suggest making only the branch starters abstract, like "Unix", "Linux", "Windows" because you will be instantiating some concrete incarnation of Windows and not an abstract, seminal, Windows concept. | |
| Jun 30, 2021 at 17:55 | comment | added | cegredev | Making the methods final is a great idea, thank you! Making the subclasses abstract won't make sense for all cases of course, but I'll definitely consider it for some. | |
| Jun 30, 2021 at 17:48 | history | edited | Tulains Córdova | CC BY-SA 4.0 |
added 7 characters in body
|
| Jun 30, 2021 at 17:38 | history | answered | Tulains Córdova | CC BY-SA 4.0 |