Timeline for Options for derived classes of two abstract base classes
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 23, 2020 at 20:17 | comment | added | Mark Lodato | After spending a few years away and learning more about design "in general", I think this ties back nicely to the first comment on the question about composition over inheritance. By injecting the type of communicator instead of inheriting from it we can hopefully avoid the "combinatorial explosion" mentioned above | |
| Dec 23, 2020 at 20:15 | vote | accept | Mark Lodato | ||
| Oct 26, 2017 at 15:51 | comment | added | Emerson Cardoso | @MarkLodato: actually, I just wanted to point that the ISendCommand instances must have a reference to some Communicator. The "Communicator communicator; " is actually useless within the interface. | |
| Oct 26, 2017 at 12:18 | comment | added | Mark Lodato | I haven't worked on that project for a while, but I'm always interested in learning! Unfortunately, I've been outside of C# for a while so I forget some details. I thought interfaces are contracts for method signatures, so what is the "Communicator communicator;" in ISendCommand? Otherwise, I do like this because it's up to the command and D classes to know the details while the communicators are general to their protocol. I'll upvote this for now and, if nothing changes in a week, mark it as the answer and check with someone on the project to see if they want to pull it in! | |
| Oct 23, 2017 at 17:50 | history | answered | Emerson Cardoso | CC BY-SA 3.0 |