JPH08263272A - Library registration method and device for common routine - Google Patents

Abstract

PURPOSE: To simplify an operation procedure for registering the common routine to a library by executing translation and connection editing in a form that only the common routine in a program is autonomously selected and registering the routine in the library. CONSTITUTION: The program 1 consists of a main routine which is not a registration object to the library and the common routine being the registration object. A load module generation part 2 selectively executes translation and connection editing on the common routine and generates the load module in an execution possible system without indicating the routine name of the registration object. In the library 3, the load modules of the common routine are registered in the system of directories, for example, and they are used in common. A processing for translating and connection-editing the library is executed only on the common routine based on autonomous selection against the common routine, and the load modules generated in connection editing are registered in the library.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for registering a library of common routines and a device therefor, and particularly when a load module is created from a common routine in a program, the name of the common routine or module to be registered, This is so that it is not necessary to specify the name of the main routine that is not registered.

Generally, a common routine is registered in a library in an executable load module format, and when the common routine is required, it is read from the library and used to translate and combine edit the common routine. So-called program parts are being implemented so as to save the trouble of executing each time.

It is desirable to improve the convenience of registration operation by eliminating the need for instructions such as routine names of common routines when the program is made into parts, and the present invention responds to such a request.

The present invention is intended for various programming languages. In the following description, as an example,
Fortran 90 introduced by this revision (January 1, 1994) is used for the concept of a module that can define common routines.

[0005]

2. Description of the Related Art Conventionally, when a load module of a common routine in a program is selectively registered in a library, that is, a load module other than the main routine is registered in the library, SELECT statement that specifies each routine name-Specifies the routine name of the main routine that is not registered
By entering the EXCEPT statement, only common routines are translated and combined and edited.

Further, in the case of a programming language in which the main routine and the common routine have a strong relationship, such as the conventional Fortran, a method of deleting the main routine part of the load modules after creating both load modules. Is also used.

[0007]

In such a conventional method, it is necessary to instruct the routine name of each common routine that is to be registered in the library and the routine name of the main routine that is not to be registered in the library. Therefore, there is a problem that the operability for registration is poor for the library creator.

Therefore, according to the present invention, only the common routine in the program is automatically and automatically selected and translated and combined to be registered in the library. It aims at simplification.

In the present specification, the term "autonomous" is used to indicate, for example, "a mode in which an instruction such as a routine registration or a module registration as a target of library registration or a target of library registration is not required". The term "translation" is used in addition to the usual concepts that include syntax analysis and semantic analysis for source programs, as well as other concepts that focus exclusively on the generation of object instructions.

[0010]

FIG. 1 is a basic configuration diagram of the present invention. In the figure, reference numeral 1 denotes a program, which includes a main routine that is not a registration target in the library and a common routine that is a registration target in the library. Two
Is a load module creation unit that creates a load module in a form that can be executed by selectively executing translation and combined editing of a common routine without any operation such as an instruction of a registration target routine name. 3 is
This is a library, and load modules of each common routine are registered in the form of, for example, a directory, and these are shared.

The outline of the processing in the load module creating section 2 is as follows. Only the common routine in the program 1 is automatically selected automatically, for example, by referring to each declaration statement. Each of the automatically selected common routines is translated to generate an object instruction. This object instruction is combined and edited to create an executable load module.

In the above processing, the steps are automatically selected and the steps are translated in any order. If the translation precedes, the main routine is also translated, and then only the translation part of the common routine is automatically translated. After selecting, move to step combination editing.

The basic configuration of the common routine library registration method of the present invention is that "a process of translating a program and then combining and editing the program is performed under the autonomous automatic selection of the common routine in the program. , The load module generated by the combined editing is registered in the library. ”

The basic configuration of the common routine library registration device of the present invention is that "a process of translating a program and then combining and editing the program is performed under the autonomous automatic selection of the common routine in the program. , A load module creation part that executes only for the common routine,
And a library for registering the load module generated by the combined editing. ”

[0015]

As described above, according to the present invention, when the common routine in the program is translated and combined and edited to register the load module in the library, the routine name of each common routine to be registered is designated, It is not necessary to instruct the routine name to exclude the main routine from the registration object, and the registration operation of the common routine to the library is simplified.

Further, it is more practical in a programming language such as Fortran 90 in which the main routine and the common routine are loosely coupled by the concept of a module in which the common routine is defined.

[0017]

Embodiments of the present invention will be described with reference to FIGS. Figure 2 shows a general-purpose MSP operating system.
It is explanatory drawing which shows the outline at the time of registering a module in an automatic call library in the case of XSP, XSP, etc.

Here, 11 is a data set (COMMON.FORT) of the Fortran program at the time of test, 12 is a module in which a plurality of common routines are defined, 13 is a main routine which is a calling program of the module 12, and 14 is A sub-object instruction data set (C.OBJ) consisting of object instructions resulting from the translation of the module 12, 15 is a control statement for combined editing created by specifying the "NAMEM" option of the Fortran 90 command, and 16 is a main routine 13. The main object instruction data set (COMMON.OBJ) consisting of the object instructions of the translation result, 17 is the combination editing for combining the object instructions of the sub object instruction data set 14 in module units to make a load module in an executable format. Program, 18 live call to register this load module Li (C.LOAD),
Are shown respectively.

The sub-object instruction data set 14
And the contents of the FORTRAN 90 (FORT90) command sequence that creates control statement 15 are: COMMON.FORT (data set 11) NAMEM (sub-object instruction Create control statement 15 for combined editing at the end of data set 14) From MODOBJ (command to output object instructions of common routine to sub-object instruction data set 14) -OBJECT (command to output object instructions of main routine 13 to main object instruction data set 16) Has become.

FIG. 3 is an explanatory diagram showing a processing procedure corresponding to FIG. 2, and the contents thereof are as follows. (31) Instruct the following and proceed to the next step. -Data set 11 to be translated- "NAMEM" option-Sub-object command data set 14 and main object command data set to which the object command is output
16 (32) Perform parsing and semantic analysis on dataset 11 and proceed to the next step. (33) Create the following object command, etc. and proceed to the next step. -Module 12 object instruction and control statement 15 for combining and editing (these object instructions and control statements are created for each module
14) Object instruction of main routine 13 (output to main object instruction data set 16) (34) Based on control statement 15, main object instruction data set 16 is ignored and sub object instruction data set For example, only 14 object instructions are selected by the difference in the declaration statement as described above, and these are combined and edited by the associative editing program 17, and the process proceeds to the next step. (35) The load module generated by this combined editing is registered in the automatic call library 18.

FIG. 4 shows that the operation system is UNI.
FIG. 21 is an explanatory diagram showing an outline when registering a module in the automatic call library in the case of X or the like, and 21 is a dataset (common.
f), 22 is a module in which a plurality of common routines are defined, 23 is a main routine that is a calling program of the module 22, 24 is a sub-object instruction data set,
Reference numeral 25 denotes a binding / editing program for binding and editing the sub-object instruction data set 24 into a load module in an executable format, and 26 denotes an automatic call library (call.out) for registering the load module.

The sub-object instruction data set 24
The contents of the command line of Fortran 90 (f90) for creating are: common.f (data set 21) -o (sub-object instruction) The object instructions of data set 24 are combined and edited into a load module in an executable format. -L call.out (instruction of file name to store load module) -N (option to generate load module of common routine) etc.

FIGS. 5 and 6 are explanatory views showing each method used in the translation and combined editing in FIG. 4, and in the case of FIG. 5, the “translation-combined editing” process is performed for each module. Running in sequence. That is, the module L1 is first translated and combined and edited, and then the module L2 is translated and combined and edited.

In the case of FIG. 6, a special instruction is inserted at the beginning or end of each object instruction of a module unit generated by the compiler, and a predetermined utility program created separately is run to set the number of special instructions. Repeatedly combine and edit.

FIG. 7 is an explanatory view showing a processing procedure corresponding to FIG. 5, and the contents are as follows. (41) Instruct the following and proceed to the next step. -Data set 21 to be translated-Execution of combined editing-File name for registering load module-"-N" option (42) Only each module 22 excluding the main routine 23 part is specified by, for example, each declaration statement These items are automatically selected and the parsing and the semantic analysis are sequentially performed, and the process proceeds to the next step. (43) The target module of the next object instruction output is specified, and the process proceeds to the next step. (44) Output the object instruction of the corresponding module to the sub-object instruction data set 24, and proceed to the next step. (45) Combine and edit the corresponding module parts of the sub-object instruction data set 24, and proceed to the next step. (46) Register the load module generated by the combined editing in the automatic call library 26, and proceed to the next step. (47) It is judged whether or not the combined editing of all the modules 22 is completed, and if "YES", the series of processes is ended, and if "NO", the process returns to step (43).

FIG. 8 is an explanatory diagram showing a processing procedure corresponding to FIG. 6, and the contents thereof are as follows. (51) Instruct the next content and proceed to the next step. -Data set 21 to be translated-Execution of combined editing-File name for registering load module after combined editing-"-N" option (52) Only each module 22 excluding the main routine 23 part These are selected by declarative statements, etc., and the syntax analysis and the semantic analysis are sequentially executed, and the process proceeds to the next step. (53) The target module of the next object instruction output is specified and the process proceeds to the next step. (54) The object instruction of the corresponding module is output to the sub-object instruction data set 24, and the special instruction is inserted at the beginning or the end of the data set 24, and the process proceeds to the next step. (55) Determine whether the processing of translation and special instruction insertion for all modules 22 is complete, and click "YES".
If, go to the next step, if no, go to step
Return to (53) (56) The utility program recognizes the next object instruction of the module unit by the special instruction, starts its combined editing, and proceeds to the next step. (57) The load module generated by the combined edit is registered in the automatic call library 26, and the process proceeds to the next step. (58) Determine whether all modules 22 have been combined and edited. If "YES", end the utility program processing, and if "NO", step.
Return to (56).

Note that the automatic selection of the module portion is executed at the time of combining and editing in the processing procedure of FIG. 3 and at the time of translation in the processing procedures of FIGS. 7 and 8, but this is merely an example. Which method is used for each processing procedure is arbitrary, and there is no special relation between the method of automatically selecting the module part and the type of operation system.

Further, in the processing procedure of FIGS. 7 and 8, instead of first executing the syntactic analysis and the semantic analysis of all the modules 22, the syntactic analysis / semantic analysis and the like and the subsequent object instruction output for each module 22. /
You may make it perform a combined edit continuously.

In the case of UNIX, for example, the process of translation-combine editing is repeated for the number of modules (see FIG. 6), and a special instruction is inserted at the beginning or end of each object instruction of each module The reason why the combined editing by the number of special commands is repeated (see FIG. 7) is that the combined editing function of UNIX is smaller than that of the general-purpose operation system.

[0030]

As described above, according to the present invention, when registering the load module for the common routine in the program into the library, these common routines are automatically selected automatically, that is, each routine name is individually designated. Even if this is not done, for example, if the option of "NAMEM" is indicated, it is automatically selected. Therefore, the operability at the time of registering the library of the common routine can be simplified.

In particular, it is practical in a programming language in which the relationship between the main routine and the common routine is weak, such as Fortran 90 which incorporates a module in which the common routine is defined.

[Brief description of drawings]

FIG. 1 is a basic configuration diagram of the present invention.

FIG. 2 is a general-purpose operating system M of the present invention.
It is explanatory drawing which shows an outline at the time of registering a module in an automatic call library in case of SP or XSP.

FIG. 3 is an explanatory diagram showing a processing procedure corresponding to FIG. 2 of the present invention.

FIG. 4 is a UNIX operating system of the present invention.
FIG. 7 is an explanatory diagram showing an outline when registering a module in an automatic call library in the case such as above.

5 is an explanatory diagram showing a method (No. 1) used in the translation and combined editing in FIG. 4 of the present invention.

6 is an explanatory diagram showing a method (No. 2) used in the translation and combined editing in FIG. 4 of the present invention.

FIG. 7 is an explanatory diagram showing a processing procedure corresponding to FIG. 5 of the present invention.

FIG. 8 is an explanatory diagram showing a processing procedure corresponding to FIG. 6 of the present invention.

[Explanation of symbols]

 In FIG. 1, 1 ... (Registration target) program 2 ... Load module creation unit 3 ... Library

Claims (10)

[Claims] 1. A process of translating a program and then combining and editing the program is executed only in the common routine under autonomous automatic selection of the common routine in the program, and is generated by the combining and editing. A method for registering a library of common routines, characterized in that the load module is registered in the library. 2. The common routine library registration method according to claim 1, wherein the common routine is defined by a module, and the processing is executed in units of the module. 3. The library registration method for a common routine according to claim 2, wherein a control statement for combined editing is added to an object instruction generated in units of the module. 4. The method for registering a library of a common routine according to claim 2, wherein the translation and the binding edit are sequentially executed for each module. 5. The common routine according to claim 2, wherein a special instruction is inserted for each module when the program is translated, and the combined editing based on the special instruction is executed via a utility program. Library registration method. 6. A load module creation section that executes a process of translating a program and then combining and editing the program only under the common routine in the program under autonomous automatic selection, and the combination. A library registration device for a common routine, comprising: a library for registering a load module generated by editing. 7. The common routine library registration device according to claim 6, wherein the load module creation unit executes the processing in units of modules in which the common routine is defined. 8. The common routine library registration device according to claim 7, wherein the load module creation unit adds a control statement for combined editing to an object instruction generated in units of the module. 9. The library registration device for a common routine according to claim 7, wherein the load module creation unit sequentially executes translation and combination editing for each of the modules. 10. The load module creation unit inserts a special instruction for each module when translating the program, and runs a utility program for executing combined editing based on the special instruction. 8. The common routine library registration device according to claim 7.