Question

This question already has answers here:

Interface implementation: declaration must be compatible (3 answers)

Closed 2 years ago.

I m在PHP OOP和打字时遇到麻烦。例如:

abstract class AC {}

class C extends AC {}

interface I {
    function method(AC $abstract);
}

class InterfaceImplementation implements I {
    function method(C $concrete) {}
}

这部法典赢得了引书,指出method与接口声明不一致。我认为,这是符合的,因为C延伸AC——我是否错了? 预计我将如何执行这种职能?

Answer 1

缩略语 B,其中也包括<代码>AC。然后,I要求其实施中的任何一项也接受<条码>B作为方法的理由。页: 1

The bigger picture: You might want to reconsider your design if you need to specify a concrete type in the implementation. The idea is that to the outside world, all that needs to be known is encoded by AC and there should not be an InterfaceImplementation that ever needs to know which concrete subclass is being transferred. Maybe the specific stuff can be embedded in C s code and generically called through a method exposed by AC?

另一项更新: 你们也许能够利用通用术语来完成你们想要的东西,但我并不认为这些东西存在于购买力平价中。我仍然想到,你是否分享设计问题的细节,这可能造成另一个令人感兴趣的问题:

Answer 2

仅将其定义为:

class InterfaceImplementation implements I {
    function method(AC $concrete) {}
}

并以C为例。 ->method(new C());。

The PHP reference Manual on 目标接口明确阐明:

执行接口的类别必须使用接口中界定的完全相同的方法签名。不这样做会造成致命错误。

友情链接