Interface ProceduralRoutineContract

Procedural routines wrap non-object oriented executional php constructs. This allows them to be approached in an object oriented manner, for compatibility with legacy architecture that does not follow an object oriented paradigm.

Appropriate use cases for this construct include wrapping procedural or imperative style files that accomplish a defined task, but assume control of operation when doing so, and do not play nice with object oriented builds.

These can then be wrapped inside a safe object, that will execute them in a safe manner upon demand, thereby decoupling their assumption of control with their standard execution approach. This is most useful in refactoring legacy code into a modern, object oriented build, in a way that does not disrupt its purpose, but allows for implementation of a different aproach to order of execution than was originally intended in a flexible way.

Contract interfaces enforce expected behavior in a non-colliding way. They are tasked with enforcing methods, and extending interfaces provided by standards and other packages for compatibility.

All valid oroboros classes MUST extend at

least one Contract Interface to be considered valid.