'. '

ImplementOnlyAbstractClass

From APIDesign

(Difference between revisions)
Jump to: navigation, search
(New page: Safer variant to ImplementOnlyInterface is to use abstract class with '''protected''' methods. Then it is clear the meaning of such methods is clear again as advocated by [...)
Line 13: Line 13:
[[Category:APIDesignPatterns:Clarity]]
[[Category:APIDesignPatterns:Clarity]]
[[Category:APIDesignPatterns:Creational]]
[[Category:APIDesignPatterns:Creational]]
-
r hand, this prevents multiple inheritance for implementors. Whether to choose the [[ImplementOnlyAbstractClasses]] or [[ImplementOnlyInterface]] is ultimately a matter of personal preference.
+
r hand, this prevents multiple inheritance for implementors. Whether to choose the [[ImplementOnlyAbstractClass]] or [[ImplementOnlyInterface]] is ultimately a matter of personal preference.

Revision as of 16:56, 12 April 2009

Safer variant to ImplementOnlyInterface is to use abstract class with protected methods. Then it is clear the meaning of such methods is clear again as advocated by ClarityOfAccessModifiers.

The NonMixedFactory.Provider interface would then become:

public abstract class Provider {
  protected abstract void initialize(Callback c);
  protected abstract int toBeImplementedBySubclass();
}

It is clear that these protected method cannot be called by anyone else except the API infrastructure. On the othe r hand, this prevents multiple inheritance for implementors. Whether to choose the ImplementOnlyAbstractClass or ImplementOnlyInterface is ultimately a matter of personal preference.

Personal tools
buy