Under an object-oriented paradigm, objects have interfaces that together provide the only access to the internals of that object.

Mixed viewpoints do not support the fundamental separation of interfaces from implementation details, which is one of the primary benefits of the object-oriented paradigm.

Rather the Cobol community is treating the language as an evolving standard that will embrace the object-oriented paradigm in a controlled, standardised manner.

It came to the conclusion that in many ways the object-oriented paradigm simply emphasises best practice for existing approaches to coding.

But how does the Cobol community move from a static, strongly typed language to the dynamic object-oriented paradigm?

The object-oriented paradigm necessitates that programs are cut up into methods that define both the data and the procedure.

Information hiding remains one of the key principles within object-oriented paradigm that promotes abstracting away the inner workings of a software program.

With these simple semantic changes we can support the whole object-oriented paradigm.

Object-Z extends Z by the addition of language constructs resembling the object-oriented paradigm, most notably, classes.

Uniquely, the object-oriented paradigm involves dynamic allocation of memory from heap storage for both object creation and message passing.