JPH03224033A - Program changing device - Google Patents

Abstract

PURPOSE:To improve the changing work efficiency by calculating automatically a revision number attending on the change of a program, storing the revision number in a control area together with the revision information, and simultaneously adding automatically the revision number to a changed row. CONSTITUTION:A program editing part 5 is activated and a line number 10 to be changed in a relevant program 8 is inputted together with the changed program data 9 equivalent to one line. Thus the program data on a designated row is changed into the input program data and a revision number 11 is written into the final position of the relevant row. If this change processing of the program data is identical with a first change processing related to the program change of this time, the present date, for example, is written in the free area of a control area 12 of the program 8 as the revision information 13. Then the revision number 11 is written in the final position of the information 13. When an end command for the change of the program data is inputted from an input device 4, a program output part 7 is activated to write the edited program 8 stored in an editing area into the same area of an original program file 1. Thus, the editing job efficiency is improved.

Description

Detailed Description of the Invention [Object of the Invention (Industrial Application Field) The present invention relates to a program changing device that changes an already created program, for example, for improvement. The present invention relates to a program changing device that records a change history on a program.

(Prior Art) Programs for controlling various devices are frequently changed for improvement.

Normally, this program modification work involves modifying, for example, a source program written in a high-level language in order to avoid complexity. Then, the modified source program is compiled and written to the actual device.

Therefore, program changes are usually performed at the source program stage.

When changing this program, it is necessary to manage the change details and the change date indicating which line of program data in the program was changed each time the program is changed, but this management is left to the person making the change.

Therefore, the method for making changes differs depending on the person who made the change, such as recording the changes in a change ledger, or creating a separate dedicated history management file and storing each program in this file. In addition, there are cases where only the revision number is written on a label formed at the top area of the program.

However, if management methods are left to each person in this way,
For example, when a single program is modified by multiple people, a great deal of effort is required to check the history of changes.

Furthermore, even if a unified management method is adopted, each changer needs to write the change contents and change date in a change ledger or manually enter keys on a keyboard, which makes it difficult for the changer to do so. This is extremely complicated work. Therefore, the work efficiency of program change work decreases.

In addition, there may be situations where the user forgets to register all of the change records, registers the wrong changes, or does not register the changes due to being busy. In such a case, there is a concern that an accurate change history will not be recorded, which may impede the next change operation.

(Problem to be Solved by the Invention) In this way, in the conventional program modification method, the work of registering changes was left to the changer, so in order to keep a complete change history, a great burden was placed on the changer. This reduces the efficiency of change work.

Additionally, there is a concern that an accurate change history cannot be guaranteed.

The present invention was made based on these circumstances, and a revision number is automatically calculated as a program is changed, is stored in a management area together with the revision information, and a revision number is automatically attached to the changed line. By doing this, when a program is changed, the change history is automatically written to the corresponding program, so the change registration work for the person making the change can be omitted, greatly improving the change work efficiency, and making it possible to always obtain an accurate change history. The purpose is to provide a program change device that can be used.

[Configuration of the Invention (Means for Solving the Problems) In order to solve the above problems, the program changing device of the present invention includes a program input unit that reads a program to be changed from a program file and writes it into an editing area; The revision number management unit determines the current revision number based on the revision number information stored in the management area of the program written in the editing area, and the revision number management unit determines the current revision number based on the revision number information stored in the management area of the program written in the editing area. A program editing section that executes editing processing, and a current revision number determined by the revision number management section is added to the line where data has been changed among the program data of each line of the program edited by this program editing section. In addition, there is a revision number addition part that adds revision information and the current revision number to the management area, and a program output part that writes the edited program to which the revision number and revision information have been added in the revision number addition part to the program file. It is equipped with

(Operation) According to the program changing device configured as described above, the program read from the program file is written into the editing area. Then, revision number information is read from the management area of the program written in the editing area, and the current revision number is determined. Then, for example, an editing process specified by the person who changed the program is executed on this program.

At the same time as this editing process is executed, the current revision number is automatically assigned to the line in which the program data has been changed. Additionally, the current revision information is written in the program management area. Then, the edited program with the revision number and revision information written is written to the program file.

Therefore, the person making the change does not need to perform any work to register the change history.

(Example) An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a block diagram showing a schematic configuration of a program changing device according to an embodiment. The program changing device of this embodiment is composed of, for example, each step of a computer processing program, and as shown in the figure, a program input section 2. a revision number management section 3 that determines the revision number for program changes; a program editing section 5 that actually edits the program according to change commands from an external input device 4; 6. Revision number addition section that attaches the previously determined revision number to each row in which data has been changed. and a program output unit 7 that writes the edited program to the original program file 1. Note that arrows in the figure indicate the flow of processing.

The program file 1 is formed, for example, on a magnetic recording disk, and stores a plurality of programs written in a high-level language for driving various devices and processing data.

FIG. 2 is a diagram showing the format of each program.

The program 8 is composed of a large number of program data 9 including instruction codes and calculation formulas, and each program data 9 is given a line number 10. Furthermore, in this program 8, an area is formed at the final position of each line in which a revision number 11 is written. This revision number 11 indicates the revision number of the entire program 8 when the program data 9 in the corresponding line is changed.

Also, at the beginning of this program 8 there is a management area 12.
is formed, and in this management area 12, revision information 13 and revision number 11 when this program is changed are recorded in chronological order. The revision information 13 includes, for example, the name of the person who changed the program in addition to the date when the program was changed as shown in the figure.

It is also possible to use short comments.

The input device 4 is composed of, for example, a keyboard, and allows the changer to enter a program number for specifying the program 8 to be changed, and a line number 10° program data 9 when actually changing the program. This is a device for inputting information.

Each of the units 2 to 7 is configured to execute a program change process according to the flowchart shown in FIG.

When the flowchart is started, the program input section 2 is activated at Sl, reads out the program 8 of the program number manually entered from the human power device 4 from the program file 1,
For example, it is written in an editing area formed in a RAM or the like. Next, in S2, the revision number management unit 3 is activated and reads out the largest revision number 11 in the management area 12 of the program 8 written in the editing area and shown in FIG. Then, 1 is added to the read revision number 11 to determine the current revision number.

Then, the program editing section 5 is activated. The program editing section is started, and in S3, the line number 10 of the corresponding program 8 to be changed and the changed program data 9 for one line.
When input, the program data of the specified line is changed (rewritten) to the manually input program data in S4.

Then, the previously determined revision number 1 is placed in the final position of the corresponding line.
Write 1.

In S6, if this program data change process is the first change process related to the current program change, the current date, for example, is written in the management area 12 of the program 8 as revision information 13 in an empty area, and further The revision number 11 determined in the above is written in the final position of the revision information 13.

Note that if the program data change processing for this line is the change processing for the second or subsequent lines related to the current program change, the current revision information 13 and revision number 11 have already been registered in the management area 12, so the program data change process will proceed directly to S8. Proceed to.

If the program data change end command is not input from the input device 4 in S8, and the next line number 10 and the changed program data 9 are input in S3, the process of changing the program data of the specified line is performed again in S4. Execute.

When a program data change end command is input from the human-powered device 4 in S8, the program output unit 7 is activated in S9. i.e. edits (changes) stored in the editing area
The completed program 8 is written in the same area of the original program file 1.

Next, each data value when the program 8 is actually changed using the program changing device configured as described above will be verified.

For example, in the program 8 shown in FIG. 2 stored in the program file 1, ■[D
] to [E], ■ Add [D-D+E] between lines 120 and 130, ■ Delete [C-C1E-ko on line 130, and ■ Further Suppose that [C] on the 140th line is changed to [D].

In this case, ■ to ■ are changed in order one by one. Furthermore, since the maximum revision number 11 of the management area 12 is [01], the current revision number 11 is [02]. Therefore, when the process of changing the program data 9 for all lines is completed, the program 8 stored in the editing area will be in the state shown in FIG. 4.

That is, current revision information 13a indicating the current date and current revision number 11a indicating [02] are additionally registered in the editing area 12. Further, the current revision number 11a of [02co] is attached to each line 110, 130, and 140 where a change in program data has occurred. Note that the data on the 120th line [B - B 10E] is not changed, so it is the previous [01
The revision number 11 remains attached. Then, in this state, it is written to the program file 1.

If the program change device has such a configuration, the program 8 will contain all the revision information 1 in case of program changes from the time the program 8 was created to the present.
3. Revision number 11 is stored in management area 12, and
The revision number 11 at the time of the change is attached to the final position of the line of the program data 9 where the change occurred. Therefore, when this program 8 is read out, a complete history of changes up to the present can be grasped.

Therefore, there is no need for the program changer to separately register the change history such as the change content, revision date and time, revision number, etc., and the changes are automatically written to the corresponding program 8, greatly improving the change work efficiency of the program changer. can be improved.

Further, since the contents of changes are automatically recorded, there is no possibility that erroneous changes will be recorded or omissions in registration will occur, so an accurate change history can always be obtained.

[Effects of the Invention] As explained above, according to the program change device of the present invention, a revision number is automatically calculated as the program is changed, is stored in the management area together with the revision information, and is automatically added to the changed line. A revision number is attached. therefore,
When a program is changed, the change history is automatically written to the corresponding program, so the change history registration work by the person making the change can be omitted, greatly improving the change work efficiency and always obtaining an accurate change history. .

[Brief explanation of drawings]

The figures show a program changing device according to an embodiment of the present invention, in which Fig. 1 is a block diagram showing the overall configuration, Fig. 2 is a diagram showing the format of the program, and Fig. 3 is a flowchart showing the operation. FIG. 4 is a diagram showing the format of an edited program. DESCRIPTION OF SYMBOLS 1... Program file, 2... Program input section, 3... Revision number management section, 4... Input device, 5... Program editing section, 6... Revision number addition section, 7... Program output section.

Claims (1)

[Claims] A program input section that reads a program to be changed from a program file and writes it in an editing area, and a current revision number is determined based on revision number information stored in a management area of the program written in the editing area. A revision number management section, a program editing section that executes externally specified editing processing for the program written in the editing area, and program data of each line of the program edited by this program editing section. a revision number addition section that adds the current revision number determined by the revision number management section to the data changed row, and adds revision information and the current revision number to the management area; and a program output section for writing an edited program to which a revision number and revision information have been added to the program file.