Skip to main content
8 events
when toggle format what by license comment
Nov 16, 2020 at 22:15 comment added Greg Burghardt I think this could be answered if you focus on the AC/DC aspect or the printer aspect. Otherwise it is too broad.
Nov 13, 2020 at 23:27 comment added Filip Milovanović "The interface for the caller is the same for AC and DC" - what is your motivation for introducing these new interfaces then? If the callers don't need to treat these differently, then there's no reason to have them. Are you anticipating future callers that will break this pattern? "I am stuck trying to understand how to make this happen" - you didn't say what you're trying to do, though. How to make what happen? I'm guessing you're not asking how to declare that one interface inherits from another, but how to design that interface for some usage scenario you have in mind.
Nov 13, 2020 at 22:52 comment added OsakaRhymes @BryanBoettcher The interface for the caller is the same for AC and DC. However, the actions taken under the hood (by the class that implements the interface) are different. There is nothing common about what happens in the implementation. However, from the perspective of the caller the outcome is the same.
Nov 13, 2020 at 22:51 answer added Karl Bielefeldt timeline score: 3
Nov 13, 2020 at 22:45 comment added Bryan B For the IVariableLoad, I now don't understand why you've introduced a separate IVariableDcLoad and IVariableAcLoad. Do those interfaces provide any AC or DC-specific behaviors? Is it better instead to have an abstract base class implementing most of the behaviors of an IVariableLoad, and then the AC/DC part specifically is implemented by subclasses?
Nov 13, 2020 at 20:50 review Close votes
Dec 2, 2020 at 3:09
Nov 13, 2020 at 20:33 review First posts
Nov 26, 2020 at 7:44
Nov 13, 2020 at 20:29 history asked OsakaRhymes CC BY-SA 4.0