JPH02308355A - Input procedure management system for interpreter - Google Patents

Abstract

PURPOSE:To easily register the flow and the control of a series of procedures as one procedure by subjecting a series of input procedures to various editing works in accordance with necessity and automatically registering the flow of this series of procedures subjected to editing as one procedure by a system. CONSTITUTION:A means 5 (table) to edit/register the flow of a series of procedures is prepared in a main routine 1 of an interpreter besides a reading-in routine 2, an interpreting execution routine 3, and an output routine 4. Conse quently, an input management table 6 is accessed to display procedures inputted till then in the order of session number, and a user can edit them in a flow chart 8. If the user wants to register edited results as a new procedure, he registers them in the table 5 and gives a name. Thus, the registered procedure is only executed in following sessions to execute plural procedures.

Description

[Detailed Description of the Invention] [Industrial Application Field] Party B's invention relates to an interpreter system equipped with means for automatically retaining input procedures and means for editing and registering the input procedures. It is.

[Conventional technology]

Generally, in interpreted systems, execution proceeds as if the user interacted with the system.

Therefore, when considering the whole process, each execution is not necessarily fast, but the advantage is that the execution process is easy to understand. It can also be said to be an optimal programming environment.

Conventionally, various systems such as LISP interpreters and UNIX shells have been used to meet these demands. These systems typically incorporate input procedure management methods.

[Problem to be solved by the invention]

These systems are suitable for re-executing individual procedures one by one, but they are suitable for re-executing the flow of a series of procedures.
It takes a lot of effort to compile and execute. Therefore, in the present invention, conventional input procedure management systems have focused only on a single hand movement, but now it is possible to focus on the flow of the input procedure and compile data.

The present invention is.

In a system, such as an interpreter system, where processing is performed through conversation with the user, a series of procedures input by the user is held.

The flow of these procedures can be arbitrarily edited whenever necessary, and the results of the editing can be automatically registered in the system as new procedures.

This is an improvement to the existing input procedure management.

The present invention focuses on a series of input procedures in an interpreter system, and aims to perform arbitrary editing on the series of procedures and register them as a new general-purpose procedure in the system.

[Means to solve the problem]

A means for editing/registering a series of procedure flows is provided in the interpreter system, and a new general-purpose procedure is constructed in the system by operating it as necessary.

[Operation] In this invention, individual input procedures automatically stored by the interpreter system are edited as necessary, and the results are newly registered in the system, so that the registered procedures can be used from the next session. You can execute multiple procedures just by executing them.

〔Example〕

An embodiment of the present invention will be shown below using two figures. FIG. 1 shows the configuration of an interpreter system. (1)
is the main routine of the interpreter, (2) is the reading routine, (3) is the interpretation execution routine, and (4) is the output routine, which are programs running on the computer system. The input procedure is executed in (3), but
The execution procedure exists in the main memory or as a file in external storage. Here, (5
), and assume that all the corresponding procedures are in main memory. Also, (6) is a relatively large table that stores the session number indicating the number of inputs and the procedure input by the user.
Assume that it exists in L.

When the interpreter main routine of destination f, +11 is started, programs f2), f31, and (4)
are executed in order. After execution of (4) is completed, (2
) is a program on a loop that performs similar operations.

Each time the loop is repeated, the session number increases by 1. Various methods can be considered for ending the interpreter main routine, but here it is assumed that the interpreter main routine ends when a certain procedure Z is executed.

The procedure read by (2) is stored in table (6) within (2) and simultaneously passed to (3).

In (3), the corresponding procedure is searched from table (5) and executed sequentially. The execution result is passed to (4).

The structure is such that it is displayed. After several sessions are performed, a database of input procedures is constructed in table (6). This database can be edited using the input procedure EDIT, and the editing results can be registered as a new procedure.

FIG. 2 is a flowchart of the program (2).

Reads the characters input by the user from the input device as a procedure. If there is an error, output an error message. The procedure was successfully entered.

It is stored in the table (6) by (71) in the flowchart. When it is stored, the session number 1 is also stored as a key at the same time.

FIG. 3 is a rough flowchart 1 of the procedure EDIT. If you enter EDIT in the input procedure, the table (5
) to be launched by you. This procedure is
Access table (6) and display the procedures entered so far in order of session number. The user edits this in step (8) in the flowchart. There are various possible forms of editing, so I will not discuss them here.

If the user wishes to create a new procedure, the result edited in (8) is registered in table (5).

At this time, the user gives the procedure a name. From now on, just enter this name and it will start. If the result of editing 1 is not to be used as a new procedure, do nothing.

〔Effect of the invention〕

As described above, according to the present invention, there is provided a means for automatically managing input procedures, a means for biasing a series of managed procedures, and a means for registering as a 9fT procedure. A series of procedure flows and controls can be easily registered as a single procedure.

[Brief explanation of drawings]

Fig. 1 is a block diagram of an embodiment of the interpreter, Fig. 2 is a flowchart of the input program of the interpreter, and Fig. 3 is a flowchart of the input program of the interpreter.
The figure shows a rough flowchart of the input procedure EDIT. In the figure, (1) is the interpreter main routine. (2) is the reading routine, (3) is the interpretation execution routine, (4) is the output routine, (5) is the procedure table, (
6 (is an input management table, (7) is an input procedure registration routine. (8) is a routine that registers the collected results as a new procedure.

Claims (1)

[Claims] In an interpreter system that interprets and executes an input procedure and outputs the result, there is a means for automatically retaining the input procedure in an editable text format in the order in which it was input, and a series of procedures retained by the retention means. an editing means that performs various editing operations as necessary for the input procedure;
An input procedure management method in an interpreter, comprising a procedure generator that automatically registers a series of edited procedure flows in a system in a format that can be executed by the system as one procedure.