词条 | Private class data pattern |
释义 |
}} Private class data is a design pattern in computer programming used to encapsulate class attributes and their manipulation. Standard documentationThe following documentation categories for the private class data design pattern follows the design pattern documentation style precedent set by the Gang of Four. Name and classification
IntentThe private class data design pattern seeks to reduce exposure of attributes by limiting their visibility. It reduces the number of class attributes by encapsulating them in single Data object. It allows the class designer to remove write privilege of attributes that are intended to be set only during construction, even from methods of the target class. Also known asPIMPL (Private IMPLementation) or Opaque pointer MotivationA class may expose its attributes (class variables) to manipulation when manipulation is no longer desirable, e.g. after construction. Using the private class data design pattern prevents that undesirable manipulation. A class may have one-time mutable attributes that cannot be declared final. Using this design pattern allows one-time setting of those class attributes. The motivation for this design pattern comes from the design goal of protecting class state by minimizing the visibility of its attributes (data). ApplicabilityThis design pattern applies to any class in any object oriented language. Structure{{Empty section|date=January 2011}}Participants{{Empty section|date=January 2011}}Collaboration{{Empty section|date=January 2011}}ConsequencesThe consequences of using this design pattern include the following:
ImplementationThe private class data design pattern solves the problems above by extracting a data class for the target class and giving the target class instance an instance of the extracted data class.
Sample codeThe following C# code illustrates an opportunity to use the private class data design pattern: The attributes radius, color, and origin above should not change after the Circle() constructor. Note that the visibility is already limited by scoping them as private, but doing methods of class Circle can still modify them. The excess exposure of the attributes creates a type of (undesirable) coupling between methods that access those attributes. To reduce the visibility of the attributes and thus reduce the coupling, implement the private class data design pattern, as follows: The Circle class in the resulting code has an attribute of type CircleData to encapsulate the attributes previously exposed to all of the methods of the class Circle. That encapsulation prevents methods from changing the attributes after the Circle() constructor. Note, however, that any method of Circle can still retrieve the values of the encapsulated attributes. Known usesThe Qt framework uses the private class data pattern in its shared libraries.[1] The classes that implement the pattern include a "d-pointer" to the data class. Methods are provided for manipulating member variables in the data class, allowing changes without breaking binary compatibility. See also
References1. ^{{cite web|url=https://wiki.qt.io/D-Pointer|title=D-Pointer |accessdate=7 January 2017}}
2 : Software design patterns|Articles with example C Sharp code |
随便看 |
|
开放百科全书收录14589846条英语、德语、日语等多语种百科知识,基本涵盖了大多数领域的百科知识,是一部内容自由、开放的电子版国际百科全书。