Plain Old Data Structures

Plain Old Data Structures (PODS) are data structures that are represented only as passive collections of field values, without using encapsulation or other object-oriented features.

Plain Old Data Structures are appropriate when there is a part of a system where it should be clearly indicated that the detailed logic for data manipulation and integrity are elsewhere. PODS are often found at the boundaries of a system, where information is being moved to and from other systems or persistent storage, and the business logic that is found in other parts of the system is not relevant. For example, PODS would be convenient for representing the field values of objects that are being constructed from external data, in a part of the system where the semantic checks and interpretations needed for true objects have not yet been applied.

A Plain Old Data Structure in C++ is an aggregate class that contains only PODS as members, has no user-defined destructor, no user-defined copy assignment operator, and no nonstatic members of pointer-to-member type. This implies that a C++ Plain Old Data Structure inherits only nonvirtually from other PODS, if at all. These restrictions ensure that the compiler or program can initialize, copy, and assign to PODS using only primitive memory copying functions and machine instructions.

In certain contexts, C++ allows only PODS to be used. For example, a union in C++ cannot contain a class that has virtual functions, or nontrivial constructors or destructors. This restriction is imposed because the compiler cannot know which constructor or destructor should be called for a union. PODS can also be used for interfacing with C, which supports only PODS.

In Java, some developers consider that the PODS concept corresponds to a class with public data members and no methods. Others would use a class that has methods but only getters and setters, with no logic. Java Beans fall under the PODS concept if they do not use event handling, and do not implement additional methods beyond getters and setters.

Other structured data representations such as XML can also be used as PODS if no significant semantic restrictions are used.

Related notes

For template-based classes in C++, it is sometimes appropriate to provide a template specialization for a PODS class that can implement moving or copying more efficiently. See Modern C++ Design.

Although it is sometimes thought that "Plain Old Data" is only an informal term that should be avoided in general communications, a POD notion is defined in ISO/IEC standard 14882 for the C++ programming language. A POD type in the standard is either a scalar type or a POD class. POD class has no user-defined copy assignment operator, no user-defined destructor, and no non-static data members that are not themselves PODs. Moreover, POD class must be an aggregate, meaning it has no user-declared constructors, no private nor protected non-static data, no bases and no virtual functions. The standard includes statements about how PODs must behave in C++.

References

*
* [http://www.fnal.gov/docs/working-groups/fpcltf/Pkg/ISOcxx/doc/POD.html "C++ Language Note: POD Types"] , by Walter E. Brown, Fermi National Accelerator Laboratory, September 29, 1999; last updated November 29, 1999.

ee also

* Plain Old Java Object