Distributable format
Translate
KOSH blueprints exist in a hardware independent, abstract format. This allows them
to exist on any hardware platform. This is achieved via a two stage model.
The first stage is to create a blueprint. For any source code written, this is
compiled into portable, neutral format. The blueprint is then frozen, packed into
a freezer and shipped to a cybersea. Once all the necessary checks have been completed
at the gate by immigration, the blueprint in thawed and goes through registration. An
additional step for blueprints is that they are registered with the blueprint manager.
The blueprint manager provides additional services required for blueprints and
co-operates with other managers in different situations.
When a request is made to build an instance of the
entity described in the blueprint, then one of the construction stages is for
the code block to be compiled from the abstract blueprint format into
a binary format suitable for execution on the underlying hardware processor.
Issues at the moment include compile at installation or execution, the transparency
of any portable format, the universality of format, and processor specific
compilation directives.
|
