JPH03144726A - Source file control device - Google Patents

Abstract

PURPOSE:To easily restore a source file by collectively controlling source files necessary for the formation of executable files in the case of updating the source files, and specifying the source file group. CONSTITUTION:When respective source files are updated, the source files are stored in an auxiliary storage device 14 based upon a format capable of extracting an optional preceding history number and source file changing history information and source file changing history control information are constituted in the device 14 in each plural source files necessary for the formation of each executable file. In each updating of an optional source file, its updating time and history number are recorded, an optional history number in an optional source file is specified and other source files are restored to the same state as the preceding state held when the updating is executed. A formation part 13 forms an executable file by using the restored source files and plural source files necessary for the formation of the executable file are collectively controlled. Thus, the source files are easily restored.

Description

DETAILED DESCRIPTION OF THE INVENTION Field of Industrial Application The present invention relates to managing the change history of multiple source files when generating an executable file by performing separate compilation using multiple source files. With the file management method (Yo), there was a function to recover the state of any history number by storing the history number, which is the ordinal number of the update, and information about the changed part regarding changes and updates of a single source file. (There is no function to collectively manage updates of multiple source files, and each source file is managed individually. Also, information regarding updates to other files is not maintained.) However, there is no way to collectively manage the change history for each of the multiple source files required to generate a file. When there is a request to restore the source files to a point in time, conventional methods manage each source file individually, so it is not possible to restore the source files all at once. In order to restore all the source files, the previous state must be restored individually based on the modification time and history number.The present invention takes into account this point. When updating a file, it is possible to collectively manage each source file necessary to generate an executable file, and use the history number of any file or any time as a key to update a group of source files rather than individual source files. The purpose of the present invention is to provide a source file management device that facilitates the restoration of source files by specifying the source file, displays source files by history number, and generates an executable file using the source files.

Means for Solving the Problems In order to achieve the above object, the source file management device of the present invention stores the change history of multiple source files and the differences from the initial file for each source file required to generate an executable file. Source file change history information to be kept, source file change history management information for managing source files using history numbers and update times, and the source file change history information and source file change history management information are stored in an auxiliary storage device. A source file storage means constructed within the system, and a source file necessary for generating an executable file are restored using the history number of any file or any time using the source file storage means as a key. The source file display section has an executable file generation section that generates an executable file.

Function: The source file management device of the present invention records the source files in an auxiliary storage device in a format from which any previous history number can be retrieved when each source file is updated, and stores the source files necessary for generating an executable file. Creates source file change history information and source file change history management information in auxiliary memory for each update, records the update time and history number every time a given source file is updated, and records the update time and history number for any source file. A source for specifying a number, restoring another source file to the same state as when it was updated, creating an executable file using the restored source file, and generating the executable file for multiple files. Figure 1 is a configuration diagram showing an implementation example of the present invention. 14 is an auxiliary storage device. ll is the change history of multiple source files,
For each source file required to generate an executable file, the source file change history is managed using source file change history information that stores difference information from the initial file, and the history number and update time that are the ordinal numbers of updates. A source file storage unit 12 that constructs source file change history management information in the auxiliary storage device 14 extracts information from the above 11 and stores any source file in file units using the history number of any file or any time as a key. Source file display i 13 has the function of specifying and displaying the history number. 13 extracts the information from 1 above and uses the history number of any source file or any time as a key to display the source files necessary to generate an executable file. FIG. 2 is a diagram illustrating the structure of source file change history information in the source file storage section of II. 20 is history information of a group of source files for generating one executable file 21 is source file change history management information 22
Source file change history information K 221 shows change history information of source file A. 221, 222 and 223
Even if .224 and .224 constitute the source files necessary to generate one executable file, the same applies to the other L. AO in 221 is the initial state of source file A, and a3 indicates difference information from history number 0 to 3 of source file A. Therefore, A3 can be found from AO and a3.

FIG. 3 is a configuration diagram of the 21 source file change history management information in the history information of the 20 source file groups. A, B, C, D are source file names,
0, 1, 2, and 3 indicate history numbers, and t(B2) indicates the time when source file A was changed from history number 1 to 2.

Figure 4 (see below) uses a flowchart to explain how to restore each source file based on the requested time IL and source file history number.
If the input value is not a history number, that is, if it is a time, then that time is used. If the input value is a history number, 42 allows source file change history management. From the information, extract the time from the history number of the source file.

In step 43, a source file that has not been accessed yet is accessed. In step 44, a history number that satisfies the time is extracted from the source file change history information. The board 45 that has accessed all the source files restores the source file group of the history number from the history number of each source file. An explanatory diagram is shown.

The horizontal axis of 51 and 52 represents each source file/k. The vertical axis represents time. The separation on the vertical axis also indicates that the source file has been updated. In this example, the initial state is tel;
The three source files, , B, and C are AQ.

Even in the state of BQ and Co, also in the current state of i&
D has been added and four source files have been added to A3.
B (J) If you want to use the history number of any source file as a key even if you are in DI status, specify the source file name and history number.
For example, to extract the source file when source file A was changed to history number 2 (
&A2, the source file change history management information in Figure 3 shows that A2 was updated at time t (B2).Furthermore, according to 45 in Figure 4, source file B includes time t (B2). The time is t (bl) and t (b2
) From this, bt is time t (B2)
is the difference information of source file B, and B1 can be found from BO and bl. Similarly, (l Do can also be found. Therefore, the state of the source file at time t (B2) is A2.
．． Bl, C large DO.

If you want to use an arbitrary time as a key, specify the time. For example, to extract each source file at time tn, i!
Search for the time that includes tn for each source file using 45 in Figure 4 in the same way as when finding it from the history number.
The state of the source file at time tn is determined from each difference information. In the case of 51, even if A1, Bl, and CL DO are obtained, the effect of the invention is greater than the effect of the invention.According to the present invention, by managing the change history of each source file using the history number and history time, the auxiliary memory The history of each source file required for generating an executable file can be collectively managed using the change history information stored in the file.

In addition, by extracting and displaying each source file using the history number and time of any source file as a key, you can easily check the previous state of the source file, and use the restored source file to It is possible to generate an executable file that depends on the history, but it is possible to generate an executable file by dividing the source files and compiling them separately (reverting one source file to its previous state and also changing the other source files. When trying to restore the state at a point in time, the user can restore all source files by simply specifying the history number or a certain time of the source file without having to restore all other source files. Amo

[Brief explanation of the drawing]

Figure 1 shows the structure of the source file change history information in the source file storage section. Figure 3 shows the structure of the source file change history management information. Figure 4 shows the structure of the source file change history management information Figure 5 is an explanatory diagram of a means for extracting a history number from source file change history management information. 11... Source file storage section 12... Source file display i 13... Executable file generation enemy l 4... Auxiliary memory disturbance

Claims (1)

[Claims] Manage the change history of source files using source file change history information that stores the change history of multiple source files for each source file required to generate an executable file, and the history number and update time that are the ordinal numbers of updates. A source file storage means for constructing source file change history management information in an auxiliary storage device, and the source file storage means stores the source files necessary for generating an executable file using the history number of any file or any time as a key. 1. A source file management device comprising executable file generation means for restoring a source file for each file and generating an executable file depending on the history.