JPS6168643A - Extension system for interpreter type language function - Google Patents

Abstract

PURPOSE:To omit a reserved language for recognizing an extended instruction and a function and merge an interpreter body with an extension function procedure automatically by providing an extension function procedure control table. CONSTITUTION:The interpreter body makes a jump to an extension function procedure side by the contents of a specific storage area when an internal flat showing whether an extension function is present or not during instruction/ junction processing is on, refers to its entry in a control table as to the extension function procedure of the lowest order, and further checks whether there is the extension function procedure is present or not at the high-order side by using EAFLAG of the control table. When this flag is on and there is the procedure at the high-order side, the control advances to the extension function procedure of the high order by the contents of its entry in the control table. When the control is returned from the high-order procedure and the instruction/ function processing is completed, the control is returned to the access origin as it is. Thus, the control is returned to the interpreter eventually.

Description

DETAILED DESCRIPTION OF THE INVENTION Technical Field The present invention relates to a method for expanding the functions of an interpreted language.
In particular, the present invention relates to a method for expanding the language functions (setting of new instructions and functions, or enhancement of the functions of instructions and functions) in an interpreter-type language processing processor that is fixed (for example, stored in a ROM).

Modification I The language function expansion (setting of new instructions/functions) for the conventional interpreter type language processing processor is carried out as follows.

(1) Decide in advance one reserved language for extended instructions/functions.

(2) The interpreter itself has a mechanism that jumps out of the interpreter memory address space with the contents of a predetermined storage area in order to transfer control to the extended instruction/function processing procedure when the reserved language is discovered during program execution. I'll keep it.

(3) Extension instructions/function processing procedures are extended to an address space separate from the interpreter main body, and specific extension functions are recognized and specified by the name following the reserved language mentioned in (1). perform the functions of

(4) Extended instructions /
It is the responsibility of the user program to set the address of the function processing procedure section. In other words, the user can
Before using a function, the address of the extended instruction/function processing procedure section must be set in a predetermined storage area.

Such a method has the following drawbacks.

The extension instruction/function must begin with a predetermined reserved language, and the user must be aware of the entry address of the extension instruction/function processing procedure. Furthermore, since there is only one storage area for transferring control to extended instructions/function processing procedures, it is impossible to use different types of extended functions in a mixed manner on the same program.

OBJECTS OF THE INVENTION It is an object of the present invention to provide an interpreter-based language function extension method that eliminates the need to specify a reserved language for recognizing extended instructions/functions, and that automatically connects the interpreter main body and extended function procedures. It is to provide.

Another object of the present invention is to provide an interpretive language function extension method that allows different types of extension functions to be mixedly used within the same program.

Structure of the Invention The interpreter-based language function expansion method according to the present invention includes a specifying means for externally specifying and storing the implementation status of an extended function procedure, and a specification means for externally specifying and storing the implementation status of an extended function procedure, and a designation means for specifying and storing the implementation state of an extended function procedure, and a specification means for specifying and storing the implementation status of an extended function procedure. Extended function procedure storage means having an address space divided into a plurality of areas corresponding to each of the Tonkuma procedures, and means for storing a control table for defining a process execution procedure of the extended function procedure specified by the specifying means. The implementation extended function procedure specified by the specifying means is executed while referring to the control table.

Example The present invention will be described in detail below using the drawings.

As shown in Figure 1, the address space for extended function procedures is set within the storage area.For example, the total number of extended function procedures is divided into 32 bytes and 4 bytes, and 8 types of extended function procedures are divided into 4 bytes. can be set in each address space, but is not limited to this numerical example. In order to indicate whether or not an extended function procedure is implemented in each address space, an extended function procedure implementation state storage area as shown in FIG. 2 is separately provided. Mounting state designation regions 11 to 8 are provided corresponding to the mounting state designation regions 11 to 8, respectively. Each area is turned on if the corresponding extension procedure is implemented, and turned off otherwise.This on/off setting is set by the user from outside, and is set before starting the interpreter. is set to

In addition, the third
An extended function procedure control table as shown in the figure is set in the storage area. EIADDRi (i=2...
- 8) stores the address of the instruction processing unit of the extended function procedure implemented directly above the i-th extended-like bear procedure. Also stored in EFADDRi is the address of the function processing section of the extended Okuma procedure that is implemented directly above the i-th extended function procedure. EAFLAGi is E IADD
This is a flag indicating whether Ri and EFADDRi are valid or not, and is used to indicate whether an extended function procedure exists at the i-th higher level.

First, the initialization process for linking the interpreter main body and the extended Kokuma procedure will be explained. The interpreter main body refers to the implementation state specification area that shows the extended function procedure implementation state in Figure 2, and according to this, performs the connection between the interpreter main body and the extended function procedure and between the extended function procedure and the same extension function procedure. In order to do so, the initialization processing section of each extended function procedure is sequentially called (assuming that the initialization processing section of the interpreter body exists at the beginning of the address space of each extended Akebono procedure). If even one extended function procedure is implemented, an internal flag indicating the existence of the extended Tonkuma procedure is set (not shown).

As shown in Figure 4, each extension function procedure is initialized so that the instruction processing section and function processing section of the extension function procedure located at the lowest level are executed first and are sequentially connected to the upper extension function procedure. In the processing section, the address of the lowest extended function procedure is set in a predetermined storage area prepared in advance on the interpreter main body side, and the control table shown in FIG. 3 is created.

Next, an instruction/function execution control system will be explained with reference to FIGS. 4 and 5. Incidentally, FIG. 4 shows an example in which extended Akebono procedures 6 and 8 are implemented.

When the interpreter itself processes an instruction/function, if an internal flag indicating the existence of an extended function is on (
As described above, this flag is set during the initialization process of the interpreter itself), and the program jumps to the extended function procedure side with the contents of a predetermined storage area without entering instruction/function processing. As described above, the address of the instruction/function processing section of the extended function procedure located at the lowest level is set in this predetermined storage area. The lowest extended function procedure refers to its own entry in the extended function procedure control table,
Furthermore, check whether there is an extended function procedure at a higher level.

This is determined by EAFLAG in the extended procedure control table. If there is no extended function procedure in the upper level, it is checked whether the instruction to be processed is the corresponding extended function. In other words, it checks whether it is something that should be handled by itself. If it should be processed by itself, it executes the processing of the instruction/function, sets an executed flag, and returns to the caller. In the case of the lowest-level extension procedure, the main body of the interpreter comes after the return.

If there is an extended function procedure at a higher level, control is transferred to the higher level extended function procedure based on the contents of its own entry in the extended function procedure control table. Similar processing is performed in the upper-level extended function procedure.

When control is returned from a higher-level extension function procedure, it is checked whether the instruction/function has been processed in any higher-level extension function procedure (checking the executed flag), and if it has been executed, it returns to the previous call. do. If it has not been executed, check whether you should process it yourself. The migration process is the same as that when no extended function procedure exists at the upper level.

In this way, control is ultimately returned from the extended function procedure to the interpreter main body/instruction/function processing section. Therefore, the interpreter itself checks whether the instruction/function has been executed in any of the extended function procedures. That is, the above-mentioned executed flag is checked, and if the execution has been completed, the process proceeds to the next instruction/function retrieval process. If it has not been executed (meaning it was not an extended instruction/function), the basic instruction/
It enters instruction/function processing as a function.

According to the present invention, there is no need to specify a reserved language that means extension instructions/functions, and the combination of extension function procedures and the interpreter body is automatically performed, and different extension function procedures can be combined. This has the effect of making coexistence possible.

[Brief explanation of drawings]

Figure 1 shows the address space for extended function procedures, °
Figure 2 is a diagram showing the extended function procedure implementation state specification storage area, Figure 3 is a diagram showing the extended function procedure control table, and Figure 4 is a diagram showing the extended function procedure implementation state specification storage area.
The figure shows an example of the combination of extended function procedures using the extended procedure control table, and FIG. 5 is a diagram showing the flow of processing between the interpreter main body and the extended function procedures when an instruction/function is executed.

Claims (1)

[Claims] This is a method for extending language functions in an interpreter-based language processing processor, which includes a specifying means for externally specifying and storing the implementation status of an extended function procedure, and a means for specifying the implementation status of an extended function procedure, and a means for specifying the presence or absence of an implementation state of an extended function procedure. Extended function procedure storage means having an address space divided into a plurality of areas corresponding to each extended function procedure, and means for storing a control table for defining a process execution procedure of the extended function procedure specified by the specifying means. An interpreter-based language function expansion method, characterized in that an implementation expansion function procedure designated by the designation means is executed while referring to the control table.