Revision as of 15:14, 5 February 2013 edit Adavidb (talk \| contribs) Autopatrolled, Extended confirmed users, Pending changes reviewers, Rollbackers 126,438 edits m Disambiguate Runtime to Run-time system using popups; formatting: whitespace (using Advisor.js) ← Previous edit		Revision as of 17:04, 26 October 2015 edit undo Androsyn (talk \| contribs) 279 edits Change occurances of C/C++ to just C++, C does not have objects and thus is not an appropriate term. Next edit →
Line 1: {{unreferenced\|date=January 2013}} Like the term [[POJO]] (''Plain Old Java Object'') 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 [[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/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 [[super class]]), or mandate component implementations to be tightly coupled to the underlying framework (calling its [[Run-time system\|runtime]]). == See also ==

Plain Old C++ Object: Difference between revisions