Timeline for Constructor from interface with minimal repetition
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 1, 2017 at 12:33 | comment | added | Guran | @Zapadlo You might very well be right. If I knew a good answer I wouldn't have asked the question :) Still, there are more clever programmers than me out there. | |
| Nov 1, 2017 at 11:33 | comment | added | Vadim Samokhin | Guran, the intrinsic nature of the approach you use implies copy-paste. Any answer would inevitably represent some shade of procedural ugliness, as I noted in my answer. The answer to your question as you posed it doesn't exist. That's why I tried to target the core problem. | |
| Nov 1, 2017 at 10:47 | comment | added | Emerson Cardoso | -1 because this is not an appropriate answer to the question. | |
| Nov 1, 2017 at 9:04 | comment | added | Guran | This is a great answer to a question I didn't ask. Yes, I could use a different OOP pattern alltogether, or go FP, but I'm asking for a way to refactor the existing solution. | |
| Nov 1, 2017 at 8:49 | history | answered | Vadim Samokhin | CC BY-SA 3.0 |