在接口和抽象类之间进行选择时要考虑哪些因素？

发布于 2024-08-19 01:04:01 字数 131 浏览 9 评论 0原文

在设计我的软件时，我从界面开始，因为这似乎是“标准”。然后我转向抽象类，因为它们似乎更适合手头的问题。然而，我不确定在做出这个设计选择时是否错过了一些考虑因素。除了我考虑过的领域特定问题之外，在接口和抽象类之间进行选择时还需要考虑哪些更一般的因素？

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

笔芯 2024-08-26 01:04:01

我发现大多数时候最好的选择是两者都做。当您依赖于基类中发生的事情时，这并不总是可能的。 同时提供抽象基类和接口可以为抽象的实现者提供最大的自由度，只要您不要求接口的实现者发生任何事情。如果您要求发生某些事情，那么您根本就不想提供接口——并且您还需要确保您的基类确保满足这一要求总是发生的行动...

两者都做的负面影响：更多的粘性。

示例伪代码：

interface IVehicle
{
    void PutCarInGear(Int speed);
}

abstract class Vehicle : IVehicle
{
    public void PutCarInGear(Int speed)
    {
        //base implementation
    }
}

请注意，在此示例中，某人可以创建自己的实现 IVehicle 的类，然后将其传递给任何采用 IVehicle 的对象。该对象不需要是 Vehicle 抽象类的子类。因此，如果您期望在 PutCarInGear() 方法中发生特定的事情，那么该新类很可能无法满足该期望。然而，只要 IVehicle 的实现做什么并不重要，那么同时拥有抽象基类和接口就是最灵活的抽象。

I find the best option most of the time is to do both. That is not always possible when you are relying on something happening in the base class . Providing both an abstract base class and an interface allows the greatest latitude by implementers of your abstraction, again, as long as you don't require something happens by an implementer of the interface. If you require that something happens, then you don't want to provide an interface at all--and you would also need to make sure that your base class ensures this required action to ALWAYS occur...

Negative to doing both: more goo.

example pseudocode:

interface IVehicle
{
    void PutCarInGear(Int speed);
}

abstract class Vehicle : IVehicle
{
    public void PutCarInGear(Int speed)
    {
        //base implementation
    }
}

Note that in this example, someone could make their own class that implements IVehicle and then pass it to anything that takes an IVehicle. That object would NOT need to be a child of the Vehicle abstract class. If, therefore, you were to expect something specific to happen in the PutCarInGear() method, it's quite likely that that new class would NOT fulfill that expectation. However, as long as it never matters what implementations of IVehicle do, then it's the most flexible abstraction to have both an abstract base class AND an interface.

回复收藏 0 原文