friend依賴性刪除重構

在軟件開發領域，朋友聲明可以引入緊密的耦合和維護問題。 This guide provides a detailed roadmap for refactoring a friend dependency properly, transforming your codebase into a more maintainable and resilient structure.

Unveiling the Need for Refactoring

Consider the following scenario: ClassA and ClassAAccessor share a friend dependency, granting ClassAAccessor access to protected members of ClassA.雖然這看起來很方便，但它帶來了幾個缺點：

UML 2.2已將朋友刻板印象置換為刻板印象。

Refactoring Step-by-Step

• Step 1: Introduce an Abstract Interface
• Replace the friend declaration with a class interface called InternalInterface, splitting the friend relationship into a direct dependency and a call dependency on InternalInterface.

Step 2: Move Operations to the Interface

Identify the operations constituting the call dependency and move them from ClassA to InternalInterface, extending InternalInterface with a protected constructor and marking ClassA's generalization association to InternalInterface as protected.

Step 3: Connect the組件

ClassaAccessor需要對InternalInterface的引用。在classa中實現附加方法，即actactAccessor（），並使用setInternalInternInterFaceref（）將其引用到ClastaAccessor。當調用Classa :: actacta :: actactaAccessor（）。 班級classaaccessor { 民眾： ClassaAccessor（Classa&Classa）; void setInternalInterfaceRef（內部接口和newValue）; 私人的： 內部接口* internalterfaceref; }; //將引用引用到Internalterface的方法 classa :: actactaccessor（ClassaAccessor&Conscontor）{ consector.setInternal Interfaceref（*this）; }