Plain Old C++ Object: Difference between revisions

Revision as of 17:04, 26 October 2015

Latest revision as of 16:45, 21 May 2025

(3 intermediate revisions by 3 users not shown)

Line 2:

Like the term [[POJO]] (''Plain Old Java Object'') in the [[Java (programming language)|Java]] world, the term '''''Plain Old C++ object''''' or its acronym '''''POCO''''' means a [[C++]] artifact that is ''neither defined by nor coupled to'' the underlying C++ component [[software framework|framework]] that manipulates it.

Examples of such an artifact include, for instance, instances of a [[C++ classes]], [[K&R C#K&R C|K&R]] [[struct (C programming language)|structs]], [[Union type|unions]], or even functions (as [[function pointers]]). This is contrast to component model in classic C++ component frameworks, such as [[Object Management Group|OMG]]-[[Common Object Request Broker Architecture#CORBA Component Model (CCM)|CCM]], [[Software Communications Architecture Reference Implementation|JTRS-SCA core framework (CF)]], Open[[Service-oriented architecture|SOA]]'s [[Service Component Architecture|SCA]] for C++. These classic component frameworks either dedicate a proprietary component programming model (a [[superclass (computer science)|super class]]), or mandate component implementations to be tightly coupled to the underlying framework (calling its [[Run-time system|runtime]]).

== See also ==

* [[Plain old data structure]] (POD)

* [[Plain Old Java Object]] (POJO)

* [[Plain Old CLR Object]] (anotheralso POCOabbreviated termPOCO)

== External links ==

* [http://code.google.com/p/pococapsule PocoCapsule/C++] An open source C++ component framework supporting plain old C++ objects.

{{C++ programming language}}

[[Category:C++]]