JPH02270034A - Module in-line evolving device - Google Patents

Abstract

PURPOSE:To increase the processing speed when a module is loaded by performing the in-line evolution of the module set at the side of a 2nd source file. CONSTITUTION:An interface check means 9 checks the number of arguments and the type of a 2nd source file 6 based on an in-line evolving instruction of a 1st source file 5. Then an argument replacement means 10 replaces the arguments of the file 6 with those of the file 5. When an internal variable name changing means 11 changes the name of an internal variable of the file 6, an external variable merging means 13 merges the external variables of both files 5 and 6 with each other. Then an in-line evolving instruction/comment conversion means 12 converts an in-line evolving instruction of a module into a comment. Thus the in-line evolution is attained for the file 6 and the module loading speed is increased.

Description

[Detailed Description of the Invention] [Objective of the Invention] (Industrial Application Field) The present invention relates to a module inline expansion device that performs inline expansion of a source file of a module body developed in the form of software based on an inline expansion instruction. .

(Prior art) A collection of processing procedures that make up a program. It takes the form of a routine where only the sentences are written and the main body is placed in a separate location.

Here, the term "routine" refers to a series of instructions or command statements in a form that can be read by a computer in order to achieve a certain set of conditions.

Therefore, by adopting a routine format, overhead occurs when calling a module, which slows down the processing speed when installing a module.

(Problems to be Solved by the Invention) As described above, in the conventional routine format described above, an overhead is generated when calling a module, so that the processing speed when installing a module is slowed down.

The present invention was made in view of the above circumstances, and an object of the present invention is to provide a module inline expansion device that can increase the processing speed when installing modules.

[Structure of the Invention] (Means for Solving the Problem) In order to achieve the above object, the module inline expansion device of the present invention expands the second source of the module main body based on the inline expansion instruction of the first source file. an interface checking means for checking the number and type of arguments of a file; an argument replacing means for replacing the arguments with arguments in the first source file; and an internal variable renaming means for renaming internal variables in the second source file. , an external variable merging means for merging external variables of a first source file and a second source file, and an inline expansion instruction commenting means for commenting an inline expansion instruction.

(Function) In the module inline expansion device of the present invention, when the interface check means checks the number and type of arguments in the second source file based on the inline expansion instruction of the first source file, the argument replacement means replaces the arguments. Replace with the argument of the first source file. Next, when the internal variable renaming means renames the internal variable in the second source file, the external variable merging means merges the external variables of the first source file and the second source file, and then converts the inline expansion instruction into a comment. means to comment out the module's inline expansion instructions.

Therefore, since the second source file can be expanded inline, overhead when calling a module can be eliminated.

(Example) Hereinafter, details of an example of the present invention will be described based on the drawings.

FIG. 1 shows a module in-line deployment device according to an embodiment of the present invention.

The module inline expansion device includes an input unit 1 that manually inputs a command to activate a module inline expansion command, and a control unit (CPU
) 2. It constitutes a part of the disk 4 of the information processing apparatus, which is composed of a display section 3 for displaying inline expansion results and a disk 4 for storing source files and the like.

The disk 4 includes a source file (A) 5 including an inline expansion instruction, a source file (B) 6 which is a source file of the module source body, a module inline expansion device 7, and an inline expanded source file (C).
Consists of 8.

The module inline expansion device 7 includes an interface check section 9, an argument replacement section 10, an internal variable renaming section 11, an expansion instruction commenting section 12, and an external variable merging section 13.

The interface check unit 9 checks the source file (A
) 5 to check the number and types of arguments in the source file (B) 6.

The argument replacement unit 10 is a source file (B) 6
Replace the argument with the argument in source file (A)5.

The internal variable renaming unit 11 renames the internal variables in the source file (B) 6.

The expansion instruction commenting unit 12 converts the source file (A) 5
Comment out the inline expansion instruction.

Here, "commenting" means commenting out the inline expansion instructions in the source file (A) 5 because they would cause an error if left as they were during compilation.

The external variable merging unit 13 merges external variables included in the source file (8) 5 and the source file (B) 6.

Next, the operation of the module inline expansion device 7 having such a configuration will be explained using FIGS. 2 to 5.

3 and 4 respectively show the contents of a source file (A) 5 containing inline expansion instructions and a source file (B) 6 of the module body, which have been created in advance. It is something.

First, when a command (instruction) is input from the input unit 1 (step 201), the module inline expansion device 7 reads the source file (^) 5 (step 20).
2) Do.

The source code is read one step at a time from the source file (A) 5 and normally output as is to the source file 8.

Here, when the inline expansion instruction of the source file (^) 5 is read, the interface check unit 9 reads the source file (B) 6 indicated by the instruction (step 203), and this source file (B) 6 and The number and types of arguments in source file (8) 5 are checked (step 204).

Next, the expansion instruction commenting section 12 comments out the inline expansion instruction of the source file (A) 5 (step 205).

Thereafter, the argument replacement unit 10 replaces the arguments on the source file (B) 6 side with the arguments on the source file (A) 5 side, including type conversion if necessary.

Further, the internal variable renaming unit 11 renames the internal variables in the source file (B) 6 (step 207).
do.

Here, it is determined whether there is an unprocessed step (step 208), and if there is no unprocessed step, the external variable merging unit 13 merges the external variables included in source file (8) 5 and source file (B) 6 (step 209). do.

In this way, in this example, when calling a module,
The module inline expansion device 7 extracts the source file (B
) 6 is expanded inline, so overhead can be eliminated, thereby increasing the processing speed when installing modules.

In addition, in this embodiment, by inline expanding the source file (B) 6, arguments are automatically replaced, which improves development man-hours and implicitly replaces internal variable names in the source file (B) 6. Since the names are changed, errors during compilation are reduced, which also improves the efficiency of program development.

Furthermore, it is possible to increase the execution speed of a program made up of source files generated by the module inline expansion device of this embodiment.

[Effects of the Invention] As explained above, according to the module inline expansion device of the present invention, the module on the second source file side can be expanded inline, so the overhead when calling the module can be eliminated. , This makes it possible to increase the processing speed when installing modules.

[Brief explanation of drawings]

FIG. 1 is a block diagram showing an embodiment of the module inline expansion device of the present invention, FIG. 2 is a flowchart showing the operation of the module inline expansion device of FIG. 1, and FIG. 3 shows the contents of the source file (A). FIG. 4 is a diagram showing the contents of the source file (B), and FIG. 5 is a diagram showing the contents of the output file. 9... Interface check section, 10... Argument replacement section, 11... Internal variable renaming section, 12.
...Expansion instruction commenting section, 13...External variable merging section Applicant: Toshiba Corporation Patent attorney Satoshi Suyama - Figure 1 Figure 2 Figure 3 Figure 4 Figure 5

Claims (1)

[Claims] (1) an interface checking means for checking the number and types of arguments in a second source file of the module body based on an inline expansion instruction of the first source file; and converting the arguments to arguments on the first source file side. Argument replacement means for replacing; internal variable renaming means for renaming internal variables in the second source file; external variable merging means for merging external variables of the first source file and the second source file; A module inline expansion device comprising: inline expansion instruction commenting means for converting the inline expansion instruction into a comment.