Timeline for How to adhere to the open-closed principle in practice
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 22, 2014 at 18:22 | answer | added | Cormac Mulhall | timeline score: 3 | |
| May 21, 2014 at 12:55 | vote | accept | Aviv Cohn | ||
| May 21, 2014 at 12:45 | history | reopened | Karl Bielefeldt AArteDoCodigo.com.br - Maniero Wayne Molina Bart van Ingen Schenau BЈовић | ||
| May 20, 2014 at 21:31 | review | Reopen votes | |||
| May 21, 2014 at 12:45 | |||||
| May 13, 2014 at 18:28 | history | closed | gnat CommunityBot jwenting gbjbaanb | Needs more focus | |
| May 12, 2014 at 16:45 | comment | added | Doval | Open/Closed Principle doesn't dictate the mechanism you use. Inheritance is usually the wrong choice. Also, it's impossible to guard against all future changes. It's best not to try to predict the future, but once a change is needed, modify the design so future changes of that same kind can be accommodated. | |
| May 12, 2014 at 15:23 | answer | added | Jeffery Thomas | timeline score: 2 | |
| May 12, 2014 at 14:38 | answer | added | Karl Bielefeldt | timeline score: 16 | |
| May 12, 2014 at 14:08 | comment | added | gnat | programmers.stackexchange.com/a/19629/31260 | |
| May 12, 2014 at 13:56 | review | Close votes | |||
| May 13, 2014 at 18:28 | |||||
| May 12, 2014 at 13:35 | history | asked | Aviv Cohn | CC BY-SA 3.0 |