Run time dynamic linking

Abstract

A platform independent binary object (PIBO) operable on disparate computing environments that have a selected hardware architecture without requiring rebuilding or reloading is provided. The PIBO can be loaded and linked with a cooperating computing application by an exemplary linker / loader, compiled and built together with the cooperating application. Also, the PIBO can be used in various contexts, including but not limited to, as a mechanism for dynamically linking shared objects on platforms that do not offer such native facility; in utilizing pre-written code components on platforms that otherwise would be incompatible due to a violation of platform constraints within particular code; as a mechanism for loading non object-oriented code that circumvents restrictions of multiple execution instances and repeat execution inherent in the code; and as mechanism that allows for the use of a binary object to add on functionality on a closed platform.

Description

technical field [0001] The present invention relates to the creation and operation of binary objects, more precisely, relates to the creation, operation and release of platform-independent binary objects that can run on different computer environments, and supports the operation of different non-local computing environments. Background technique [0002] A computing environment is capable of executing computer code, comprising one or more instructions, designed for hardware components of the computing environment to perform one or more operations. Typically computer code is loaded into a computing environment for execution. Before being physically loaded, computer code may be compiled to enable operation in a particular computing environment (eg, computing environment operating system and / or computing environment platform). Computer code can be linked by a computing environment to other computer code residing in the computing environment to perform one or more operations. ...

AI Technical Summary

Problems solved by technology

However, the scope of such reuse is limited because current practice requires the development and customization of additional components (e.g., libraries, functions, data structures, etc.) platform) can be operated

[0007] Traditional practices and approaches have other limitations, including, but not limited to, the inability of a single platform-independent binary object to operate across different computing environments without rebuilding or recompiling for each different computing environment

Furthermore, current practices and approaches do not provide mechanisms for dynamic linking of shared objects in platforms that do not provide native support for

At the same time, in current practice, pre-written code components may be incompatible due to violation of platform restrictions in specific code, so that they cannot be used in the platform

Furthermore, current practice provides no mechanism for the loading of non-object-oriented code that can bypass the limitations of multi-execution instances and the inherent loop execution of the code

At the same time, current practices and approaches do not provide mechanisms to allow dynamic linking and loading of binary objects in closed platforms (e.g., platforms that restrict the execution of additional programs)

Images