Call method between chip

Abstract

The invention relates to an inter-component calling method, comprising: 1) establishing a fixed identification and a component establishing function for each component to establish a component interface; 2) a program is loaded into a preset shared memory and triggers to store the component identifications and the component establishing function into the shared memory; 3) a client component requests to call an object component, and the system finds identification of the object component to call the function to establish a component and returns an object component interface, and the client component implements function call according to the object component interface. The inter-component call does not depend on a specified operating system, thus making the method able to be implemented between operating platforms. And the inter-component call is relatively simple, raising software development efficiency.

Description

technical field [0001] The invention relates to a program execution method, in particular to a calling method between components in the program execution process. Background technique [0002] Application program: an executable file (Executable program) refers to a computer program developed to run on an operating system in order to complete a certain task or several specific tasks. It conforms to a certain format specified by the operating system and is stored in binary form, and the operating system is responsible for loading and running the program. [0003] Early programming did not have the idea of ​​components, and all functions were concentrated in one executable file. Today, applications are usually written by dividing them into multiple relatively independent components based on their functions. Each component is relatively independent, and the components call each other through the interface. When a functional requirement changes, on the premise of keeping the i...

AI Technical Summary

Problems solved by technology

At the same time, in order to form a unified component development and call specification on the Windows platform, to realize the communication between components and the call between components, Microsoft proposed the method of Component Object Model (COM, Component Object Model), but because of its calling mechanism, the A large amount of code needs to be written before the implementation of calls between components and components, clients and components, and the implementation is complicated; and, since COM components must be registered in the registry to obtain the component ID, the component is loaded by looking up the registry when calling, however, The registry exists only on the Windows platform, so components developed based on COM cannot be transplanted across operating systems

Images