Plain Old C++ Object: Difference between revisions

Content deleted Content added
Replacing deprecated {{wikify}} with {{underlinked}}
Alexbee2 (talk | contribs)
Improved awkward phrasing
Tags: Mobile edit Mobile app edit iOS app edit App section source
 
(8 intermediate revisions by 8 users not shown)
Line 1:
{{underlinkedunreferenced|date=OctoberJanuary 20122013}}
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.
{{orphan|date=December 2007}}
Like the term ''plain old Java object (POJO)'' in the [[Java (programming language)|Java]] world, the term '''''Plain Old C/C++ object''''' or its acronym '''''POCO''''' means a [[C++|C/C++]] artifact that is ''neither defined by nor coupled to'' the underlying C/C++ component framework that manipulates it. Examples of such an artifact include, for instance, instances of a C++ classes, K&R structs, unions, or even functions (as function pointers). This is contrast to component model in classic C/C++ component frameworks, such as OMG-CCM, JTRS-SCA core framework (CF), OpenSOA's SCA for C++. These classic component frameworks either dedicate a proprietary component programming model (a super class), or mandate component implementations to be tightly coupled to the underlying framework (calling its runtime).
 
Like the term ''plain old Java object (POJO)'' in the [[Java (programming language)|Java]] world, the term '''''Plain Old C/C++ object''''' or its acronym '''''POCO''''' means a [[C++|C/C++]] artifact that is ''neither defined by nor coupled to'' the underlying C/C++ component 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/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)]], OpenSOAOpen[[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]]
 
== ExternalSee linksalso ==
* [[Plain old data structure]] (POD)
* [[Plain Old Java Object]] (POJO)
* [[Plain Old CLR Object]] (also abbreviated POCO)
 
==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++]]