JP2010067103A - Error information output device, error information output method and error output program for program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To obtain an error information output device, an error information output method and an error information output program of a program for improving the efficiency of the correcting operation of an error on the description of a program. <P>SOLUTION: This error information correction device for correcting the error of a program is configured to read a source code 105 by a source code reading part 106, and to analyze a syntax by a syntax analyzing part 107, and to detect an error on description. An error information analyzing part 108 analyzes an error other than the error clarified in the past by a source correction information database 109 by a factor, and performs temporary correction so that an error can be prevented from being detected from the analytic result, and stores temporary correction in a correctable information storage region 113<SB>1</SB>, and stores an uncorrectable error in an uncorrectable information storage region 113<SB>2</SB>, and performs error display. Thus, the error display can be simplified and the correction of the error stored in the correctable information storage region 113<SB>1</SB>can be simplified. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to an error information output device, an error information output method, and an error information output program that output error information when there is an error in the description of a program, such as when a compiler detects an error in source code.

  A description will be given using a compiler as an example. The compiler statically checks the grammar of the source code it interprets. If there is an error when converting to the machine language code, an error message is displayed as a compile error in association with the line in which the code is described.

  By the way, when a source code is created, the same error is often repeated at a plurality of locations. For example, when describing source code, suppose that you forget to describe a variable definition or that the description is incorrect. Then, whenever a description that refers to the definition occurs, an error occurs that the definition of the reference destination does not exist.

  In such a case, the first related technique of the present invention displays the same error in many lines that refer to the same definition in the source code, even though the error originally occurred due to one cause. (For example, refer to Patent Document 1). As a result, even if an error other than this error exists in the source code, the latter error display is buried in many error displays indicating the former error, and the latter error itself is overlooked. There was a case. In the first related technique, the output of a neural network is used as a method for organizing error information. However, there is no specific disclosure about the output mode for errors, and its feasibility is low.

  Thus, as a second related technique of the present invention, a proposal has been made to simplify the display by performing only the necessary error display (see, for example, Patent Document 2). In the second related technique, the contents of the corrected error are stored. If the same error has occurred in the lines after that line, instead of displaying the error, a predetermined mark such as “@” is displayed or the display is deleted. .

  By the way, an error display for an error in the description of the program is for the program creator to make corrections. In the third related technique of the present invention, not only the error in the description of the program is displayed but also the error is parsed. The type of error is displayed, and if possible, the error is automatically corrected (see, for example, Patent Document 3).

  In the third related technique, past correction information for errors occurring in the program is stored in the error correction history storage means. In addition, when there are errors in the program that are the same as those of past corrections, their attributes are displayed for each error. If the same error as the error stored in the error correction history storage means exists in the program, the corresponding program is corrected. In addition, when an error that is not stored in the error correction history storage means occurs, this is output together with the attribute of the error.

However, even if errors corrected in the past using the error correction history storage means are not displayed in the program description, error display may still occur frequently depending on the contents of the described program. Therefore, in the fourth related technique of the present invention, error display is avoided for a specific type of error message that does not require program correction as a result of error parsing (for example, Patent Document 4). reference).
JP 04-365134 A (paragraphs 0008 and 0009, FIG. 1) Japanese Unexamined Patent Publication No. 09-016437 (paragraphs 0014 to 0018, FIGS. 2 and 3) JP-A-11-085536 (paragraphs 0008 and 0011, FIG. 6) Japanese Patent Laying-Open No. 2004-206501 (paragraphs 0006 and 0007, FIG. 1)

  According to the fourth related technique, it is possible to efficiently avoid the output of an error message that is known to require no program correction, and therefore it is possible to reduce the load required for investigating the cause of the error.

  However, even with the fourth related technique, until a certain amount of history information is stored in the error correction history storage means, there is a high possibility that many errors are displayed at the place where the program is described. Therefore, for example, when an error correction is to be started for a new program description, this is a major cause of hindering the efficient work of the person who performs the error correction work.

  SUMMARY OF THE INVENTION An object of the present invention is to provide a program error information output device, an error information output method, and an error information output program that can improve the efficiency of correcting errors in the description of a program.

  In the present invention, (b) error detecting means for detecting errors in the description of the program to be inspected in order along the described lines, and (b) analyzing each error detected by the error detecting means. Error cause identification means for determining whether or not the cause of the error can be identified for each error, and (c) the error identified by the error detection means described above for each cause for the error identified by the error cause identification means. (D) temporary correction error output means for outputting the above-described error of the program corrected by the temporary correction means as a group, (e) ) Individually indicating the location of each error that cannot be corrected by the temporary correction means in the program to be inspected. To and a over location information output means to the error information output device program.

  In the present invention, (b) an error detection step for detecting errors in the description of the program to be inspected in order along the described line, and (b) each error detected in the error detection step is detected. An error cause identifying step for analyzing and determining for each error whether or not the cause of the error is identified, and (c) the error identified in the error cause identifying step by the error detecting step described above for each cause. A temporary correction step for performing a temporary correction such that no error is detected; and (d) a temporary correction error output step for outputting the above-mentioned errors of the program corrected by the temporary correction step as a group. (E) An error that cannot be corrected by the temporary correction step described above in the program to be inspected. There each location is provided to the error information output method of the program and an error location information output step shown individually of.

Furthermore, in the present invention,
As a program error information output program to a computer that corrects an error in the description of the program to be inspected, (a) an error detection process for detecting the error in the program description described above in order along the described lines; (B) Error cause identification processing that analyzes each error detected in this error detection process and determines whether the cause of the error is specific for each error, and (c) This error cause identification processing causes the cause. A temporary correction process for performing a temporary correction for the identified error so that the error detection process is not performed according to the cause, and (d) the program corrected by the temporary correction process. Temporary correction error output processing that outputs errors as a group, and (e) in the program to be inspected as described above. It is characterized in that to perform the error location information output process shown individually each location of the error can not be corrected by the provisional correction process described above.

  As described above, according to the present invention, an error in program description is specified for each cause, and for the error for which the cause can be specified, provisional correction is performed so that no error is detected. , These errors are output as a group. As a result, errors that cannot be corrected can be made obvious, and these corrections can be performed reliably. In addition, since errors that have been tentatively corrected are directed to correct errors, the correction work can be performed efficiently with reference to this. Further, such an error may be completely corrected by temporary correction on the apparatus side, and there is an advantage that it does not take time to correct such an error.

  Next, the present invention will be described together with an embodiment.

  FIG. 1 shows an outline of the error information correcting apparatus according to the present embodiment. The error information correction apparatus 100 includes a CPU (Central Processing Unit) 101 and a main control unit 103 having a memory 102 that stores a control program executed by the CPU 101. The main control unit 103 is connected to a source code reading unit 106 that inputs a source code 105 as a program to be inspected from outside via a data input unit such as a communication network or a memory card (not shown). Further, the main control unit 103 analyzes the syntax of the source code read by the source code reading unit 106 line by line, and the type of error information when there is an error in the syntax. An error information analysis unit 108 and a source correction information database 109 that stores source correction information for analyzing error information are connected.

The error information correction apparatus 100 visually displays an operation input unit 111 including a keyboard and a pointing device (not shown) for inputting an operation of an operator who corrects an error, and various types of information such as a source code error. A display unit 112 such as a liquid crystal display and a data storage unit 113 that stores various data such as a source code before correction read by the source code reading unit 106 and a source code after correction are provided. Various data can be stored in the data storage unit 113. A correctable information storage area 113 ₁ for storing “correctable error information” as information that can be corrected, which will be described later, and information that cannot be corrected An uncorrectable information storage area 113 ₂ for storing “uncorrectable error information” is provided.

  At least a part of each component constituting the error information correction apparatus 100 may be configured by hardware as a circuit component, but is functionally configured by software realized by the CPU 101 executing a control program. It may be a thing. A printer that prints out various information such as error information may be prepared instead of the display unit 112 that performs visual display.

  Of these components of the error information correction apparatus 100, the circuit function part that outputs data relating to errors in the source code reading unit 106, the syntax analysis unit 107, the error information analysis unit 108, and the display unit 112 is generally called a compiler. ing. However, the compiler has various configurations, and in this embodiment, regarding the display of the error information on the display unit 112, a convenient device is provided for the operator's source code correction operation as described later. .

  FIG. 2 shows an outline of control of the apparatus from reading the source code to be corrected by the error information correcting apparatus until outputting error information. This will be described with reference to FIG.

  It is assumed that the error information correction apparatus 100 is turned on (not shown) and the operator instructs the operation input unit 111 to start reading the source code 105. Then, the source code reading unit 106 reads only one line from the top of the source code 105 (step S201). Of course, the source code reading unit 106 reads the entire source code 105 in advance, stores it in a specific area in the data storage unit 113, and reads it in units of one line when inspecting each row. It may be.

  The source code reading unit 106 checks whether or not the read one line is the last line of the source code 105 (step S202). Here, since the source code of the first line is read, it is not the last line yet. Therefore, the read source code for one line is sent to the syntax analysis unit 107 to execute syntax analysis (step S203). The syntax analysis unit 107 outputs whether or not an error is found as a result of the syntax analysis. If no error is found as a result of this parsing (step S204: N), the process returns to step S201, and the source code for the next line is read.

  On the other hand, if an error is found in step S204 (Y), it is determined whether the error is an error existing in the source correction information database 109 (step S205). In the source correction information database 109, errors whose correction contents are known in the past correction work and those correction contents are stored in comparison. Therefore, if the error is the same as the error stored in the source correction information database 109 (Y), the correction is performed (step S206). In this case, after the error is corrected, the process returns to step S201 again to start reading the next line. The above processing has been performed conventionally.

On the other hand, if it is determined in step S205 that the corresponding error does not exist in the source correction information database 109 (N), whether or not the error can be corrected by a later operation by the operator. Is determined (step S207). A determination method for this will be described in detail later. As a result, in the case of an error that can be corrected later by the operator (Y), “correctable error information” to which information for suggesting the direction of correction to the operator is added is generated (step) S208). Then, this is stored in the correctable information storage area 113 ₁ of the data storage unit 113 (step S209). And it returns to step S201 again and reading of the following 1 line is started.

On the other hand, if the error can be corrected by the operator in step S207, the error that is not determined by the error information correction apparatus 100 side is (N) as “uncorrectable error information”, and the uncorrectable information storage area 113 ₂ of the data storage unit 113 (Step S210). And it returns to step S201 again and reading of the following 1 line is started. However, in determining whether it is “correctable error information”, it may not be possible to determine only by the corresponding one-line source code. In such a case, the source code reading unit 106 needs to prefetch the source code 105 to some extent. This will also be described later.

Thus, returning to step S201, the source code 105 is read line by line, and the processing described above proceeds in line units. As a result, it is determined that the source code 105 read at a certain time constitutes the last line (step S202: Y). In this case, it is checked whether “correctable error information” is stored in the correctable information storage area 113 ₁ (step S211).

When “correctable error information” is stored in the correctable information storage area 113 ₁ by this series of reading of the source code 105 (Y), all the source codes read by the source code reading unit 106 are processed. Then, duplicate “correctable error information” is integrated. For example, if the same “correctable error information” exists in the first row and the tenth row, this is set as information corresponding to the first row as one “correctable error information”. In this way, correction information is created as information that can be immediately corrected by the operator (step S212). Then, the correction information and the “uncorrectable error information” stored in step S210 are output as information for instructing the operator (step S213). If “correctable error information” is not stored in the correctable information storage area 113 ₁ in step S211, (N), the process of step S213 is omitted and the process of step S213 is performed.

  The uncorrectable error information may be output in step S213 in a form in which “correctable error information” and “non-correctable error information” are completely separated on the screen or as a printout. Alternatively, “correctable error information” and “non-correctable error information” may be displayed in correspondence with each other so as to be distinguished from each other in a series of source codes.

  As described above, in the present embodiment, when errors exist in the source code and this is based on mistakes that are easy to be mistaken for the creator of the source code, the error information correcting apparatus 100 treats them as “correctable errors”. "Information". Then, by showing these to the operator as a group different from the “uncorrectable error information”, the error can be corrected early. At this time, in the present embodiment, the error information correction apparatus 100 implements an example of a solution for solving the error so as to realize a situation in which no error has occurred on the surface.

  On the other hand, for “uncorrectable error information”, work without knowledge of the source code is performed, or when the operator performs typing with a wrong character conversion setting for the keyboard (not shown). In many cases, the correction is not possible and the correction cannot be performed mechanically. Therefore, in the case of “uncorrectable error information”, the error information correcting apparatus 100 cannot solve the error even on the surface. The operator needs to consider the cause of the error.

  One feature of the error information correcting apparatus 100 according to the present embodiment is that the correction work is facilitated by making it possible to correct “uncorrectable error information” separately from “correctable error information”. . Accordingly, some typical examples of what can be regarded as “correctable error information” will be exemplified, and the principle of apparently eliminating these errors will be described below.

  FIG. 3A shows an example of a source sentence with missing definitions as a first example in which an error occurs. In this source example 301, C # (Sea Sharp) is used as a language, but the definition of the variable “op2” is not described. For this reason, the variable “op2” is not found in the function call portions of both “obj.Method” 321 and “obj.Method2” 322 thereafter, and an error occurs in these two lines. Detection of an error due to forgetting such a definition can be performed by checking whether there is a description of the definition in the previous source sentence when there is a function call part.

  FIG. 3B shows another example of source correction information for adding a necessary definition to a source sentence. Before the operator corrects the error, the error information correcting apparatus 100 shown in FIG. 1 can form the definition as the source correction information 302 for the variable “op2” to eliminate the error. . In the case of the first example, the variable “op2” may be indicated as one of the “correctable error information”, and the operator may define the variable “op2”.

  FIG. 4A shows an example of a source sentence with missing definitions as a second example in which an error occurs. In this source example 303, C # is also used as the language. In the case of this example, there is no description of “}” corresponding to the delimiter (bracket symbol) “{” used in the “if statement” 331. In such a case, as a compiler, when “public long BBB () {” 332 is read in accordance with language specifications, an error occurs because an invalid definition exists in the method.

  FIG. 4B shows an example of source correction information for adding a necessary delimiter to a source sentence. Here, the delimiter character “}” associated with the delimiter character “{” is added as the source correction information 304. That is, the error information correcting apparatus 100 side shown in FIG. 1 indicates the delimiter “}” as one of the “correctable error information”, and it is suggested that the error is corrected with the delimiter “}”. In the case of the second example, it is determined whether or not it corresponds to “correctable error information” by sequentially checking whether the character indicating the start and the character indicating the end are taken in the delimiter. can do.

  FIG. 5A shows an example of a source sentence using a variable not suitable for calculation as a third example in which an error occurs. In this source example 305, “2” is assigned to a variable “data” of “String type” or used as a calculation variable. In this case, the usage of the variable is incorrect and it is necessary to correct it to a variable suitable for calculation. Taking C # as an example, there are several types such as “int type”, “long type”, and “short type” that can be used for calculation. Which type to use is determined by the operator who modifies the source code.

  FIG. 5B shows an example of source correction information as a type that can be used for calculation. The error information correcting apparatus 100 shown in FIG. 1 only needs to indicate one of the “correctable error information” for suggesting the direction of correction, and it is not necessary to specifically indicate the correction contents. Therefore, as shown in FIG. 5B, an example is shown in which the variable “data” is modified to “int type” that can be used for calculation. In the case of the third example, it is possible to determine whether or not the variable corresponds to “correctable error information” by checking whether or not a variable that is not suitable for the calculation is erroneously used in the calculation.

  FIG. 6A shows an example of a source sentence in which the “import sentence” of the referenced class is missing as a fourth example in which an error occurs. This source example 307 is an example of Java (registered trademark) (Java) language. In this example, the “import statement” of the referenced class is missing. For this reason, an error occurs that the class cannot be found in all places where the class is used.

  FIG. 6B shows an example of source correction information for adding an “import sentence”. In this way, when a class can be resolved by a compiler, it is determined whether or not it falls under “correctable error information” by checking whether or not “import statement” is missing as in the source correction information 308. Can do.

  FIG. 7A shows an example of a source sentence in which the destination label of the “goto sentence” is missing as a fifth example in which an error occurs. In this source example 309, C language is shown as an example. In the “goto statement”, an unconditional jump is made to the specified label or line number, but no label is specified.

  FIG. 7B shows an example of source correction information that has been corrected to add a temporary label. When a “goto statement” exists like the source correction information 310, it can be determined whether or not it corresponds to “correctable error information” by checking the presence or absence of the “goto statement”.

  FIG. 8A shows an example of a source sentence in which a procedure name to be repeated is missing as a sixth example in which an error occurs. In this source example 311, COBOL (COmmon Business Oriented Language) language is shown as an example. Since there is no procedure name (TETUDUKI) to be repeated, an error occurs at a location 341 that specifies a procedure name that does not exist.

  FIG. 8B shows an example of source correction information that has been corrected to add a procedure name. By adding a procedure name like the source correction information 312, this error is solved. In this sixth example, it is possible to determine whether or not the procedure name to be repeated exists in the source sentence, so that it corresponds to “correctable error information”.

  FIG. 9A shows an example of a source sentence whose headline is an invalid word as a seventh example in which an error occurs. In this source example 313, the COBOL language is shown as an example. In the COBOL language, there is always a fourth procedure division (PROCEDURE DIVISION) describing an actual program. However, in this source example 313, the heading “PROCERE DIVISION” 351 is an illegal word. In such a case, the subsequent description is described in an illegal position. As a result, an error occurs.

  FIG. 9B shows an example of the source correction information edited to the correct heading. As in the source correction information 314, the error is resolved by editing “PROCEDURE DIVISION” into a correct heading. In the seventh example, it is only necessary to check whether an illegal word is described in a place where a keyword such as “DIVISION” exists. If such an invalid word is present, it can be determined that it corresponds to “correctable error information”.

FIG. 10 specifically shows the error information analysis unit. The error information analysis unit 108 determines that the syntax analysis unit 107 shown in FIG. 1 has an error in the source code 105 and stores these errors as corrected in the source correction information database 109. The error analysis is performed for those that are not. Then, the information analysis is successful with this error information analyzing unit 108, as a "correctable error information" is stored in the modifiable information storage area 113 ₁ shown in FIG. 1, the information analysis is not successful, "Modify It is stored in the uncorrectable information storage area 113 ₂ as “impossible error information”.

Such an error information analysis unit 108 includes first to mth analysis units 131 _{1 to} 131 _m . Here, the first analysis unit 131 ₁ has a function of analyzing and detecting errors related to the first example described in FIG. 3 and the third example described in FIG. 5, for example. Further, the second analysis unit 131 ₂ includes a function of detecting and analyzing the error for the second example described with reference to FIG. 4, for example. 3 to 9 show the first to seventh examples. However, these are only examples, and appropriate types of errors are analyzed and detected by the _{first to} mth analysis units 131 _{1 to} 131 _m . Will be.

  Further, the error information correction apparatus 100 and the error information analysis unit 108 according to the present embodiment are configured as general-purpose apparatuses corresponding to various languages such as C, C #, Java (registered trademark), and COBOL. . Of course, the error information correction apparatus 100 may be an apparatus corresponding to only one language. In this case, the error information analysis unit 108 only needs to include the analysis unit 131 specialized for the language to be handled.

FIG. 11 shows the first analysis unit more specifically. Note that the second to m-th analysis units 131 _{2 to} 131 _m may also be configured to embody the error detection principles illustrated in FIGS. 4 to 9, respectively. It is not particularly limited. Therefore, illustration and description of the details of the _{second to} m-th analysis units 131 _{2 to} 131 _m are omitted.

The first analysis unit 131 ₁ performs a first analysis that executes a definition data table 141 in which variables related to the analysis are registered in advance and an analysis procedure for analyzing and detecting an error related to the first example described with reference to FIG. A procedure execution unit 142 is provided. Here, the first analysis procedure execution unit 142 may include a storage medium that stores a unique CPU and a control program executed by the CPU. Further, the CPU 101 shown in FIG. 1 may execute the control program stored in the memory 102 so that the first analysis procedure execution unit 142 is realized in software.

  FIG. 12 shows a state of processing executed by the first analysis procedure execution unit. This will be described with reference to FIGS. 1, 3, 5 and 11.

  In the source example 301 in FIG. 3A, there is a description “ret = obj.Method (op1, op2)”. This is a description for calling the function “Method” using the variables “op1” and “op2” as arguments. Normally, when a variable is used, the compiler checks whether the variable is defined. First, for the variable “op1,” the variable definition is checked. Specifically, it is checked whether or not there is a variable definition in the definition data table 141 in this case, in the definition data table that the compiler internally has (step S231). In FIG. 3A, “int op1;” is described in advance, and “int variable op1” is defined. For this reason, the variable “op1” is already defined (Y).

Therefore, the process proceeds to step S232. In step S232, it is checked whether the variable type matches the method argument type. In the source example 301, the definition of the “Method function” is “public int Method (int a, int b)”, the argument type is “int”, and there is type information (Y). Therefore, the variable “op1” has no error, and is excluded from the processing of the _first analysis unit 1311 that determines whether or not “correctable error information” is output when an error occurs. . Therefore, in this case, the process for the variable “op1” ends as it is (end).

  Next, error checking for the variable “op2” will be described. Even in the case of the variable “op2”, it is checked whether there is definition information in the definition data table 141 in step S231. In this case, there is no description that defines the variable “op2” in advance. Therefore, there is no definition (N). Accordingly, the process proceeds to step S233, and it is determined whether or not the variable “op2” is defined in the source correction information database 109 shown in FIG. If it is defined (Y), the process proceeds to step S232 to check whether the type of the variable matches the type of the argument of the method. If there is type information (Y), the process for the variable “op2” ends as it is (end).

  If there is no type information (step S232: N), it is determined whether or not the variable type is corrected in the source correction information database 109 (step S234). If it has been corrected (Y), there is no problem, and the process ends as it is (end).

If there is no type information (step S232: N) and the variable type is not corrected in the source correction information database 109 (step S234: N), the variable type is corrected (step S235). . Then, this is output as “correctable error information” in order to present it to the operator (step S236), and the processing of the first analysis procedure execution unit 142 is ended (END). This “correctable error information” is finally stored in the correctable information storage area 113 ₁ .

  On the other hand, if it is determined in step S233 that the variable “op2” is not defined in the source correction information database 109 (N), it is defined as “int op2” as a variable for eliminating the error output, This is registered in the source correction information database 109 (step S237). Then, this state is output as “correctable error information” in order to present it to the operator (step S236), and the processing of the first analysis procedure execution unit 142 is ended (END).

  Next, processing when the description of “ret = obj.Method2 (op1, op2)” in FIG. 3 is read will be described. The processing for the variable “op1” is as described above.

  For the variable “op2” of “ret = obj.Method2 (op1, op2)”, first, it is checked whether or not there is a variable definition in the definition data table (step S231). Since it has not been defined, the process proceeds to step S233, and it is determined whether or not the variable “op2” is defined in the source correction information database 109 shown in FIG. In this case, the definition of the variable “op2” is registered in the source correction information database 109 in the previous step S237 (step S233: Y). Therefore, the process proceeds to step S232. In this example, type information is originally undefined. Therefore, the source correction information database 109 is searched to obtain “int op2” as a variable for eliminating the error output. As a result, subsequent redundant error output for the variable “op2” can be suppressed.

  Next, processing of the source example 305 in FIG. 5A will be described. The variable “data” is defined as “String type” that can store character strings. “Data2” is defined as an “int type” that can store an integer. First, in “data = 2”, the integer “2” is stored in the variable “data”. In this case, in the variable definition check in step S231, the variable “data” is defined (Y). Therefore, the process proceeds to step S232. In step S232, the variable type is checked. Here, since an integer is stored in a variable that can store a character string, there is no type (N). Therefore, the process proceeds to step S234.

  In step S234, there is no information to be searched in the source correction information database 109 (N). Therefore, the process proceeds to step S235 to correct the variable type. In this case, the type of the variable “data” is changed to “int type” so that an integer can be stored. Then, this is output as “correctable error information” in order to present it to the operator (step S236), and the processing of the first analysis procedure execution unit 142 is ended (END).

  In “data2 = data * 2” in FIG. 5A, the variable is similarly checked. In this case, an arithmetic instruction that doubles the variable “data” and stores it in “data2” is used. "String type" cannot be used for arithmetic instructions. Therefore, in this case as well, it is determined that there is no type in step S232 in which the variable “data” is checked (N). Therefore, the process proceeds to step S234, and it is determined whether the corrected information is registered in the source correction information database 109. In this case, information changed to “int type” with “data = 2” is registered (Y). Therefore, the process ends as it is without outputting an error (end). In this case also, redundant errors are suppressed.

  As described above, according to the present embodiment, it is possible to suppress compile error messages of the same cause, and the efficiency of correction work is improved. In addition, for errors that can determine the direction of error erasure without going through the operator, the error message output is avoided and these are presented to the operator together, so there is an oversight of points to be corrected. There is an advantage that it is difficult to occur.

  <Modification of the invention>

  FIG. 13 shows the configuration of an error information correction apparatus according to a modification of the present invention. In FIG. 13, the same parts as those in FIG. 1 are denoted by the same reference numerals, and description thereof will be omitted as appropriate.

  In the error information correction apparatus 100A of this modification, a correction source generation unit 115 is newly provided. The correction source generation unit 115 generates source difference information 117 representing a difference between the correction source 116 corrected in advance and the original source, using the source correction information in the source correction information database 109 accumulated as a result of compilation. It is a function to do. The corrected source 116 and the source difference information 117 are output as visual information by the display unit 112. Of course, the correction source 116 and the source difference information 117 may be printed out by using a printer (not shown). The main control unit 103A includes a memory 102A that stores a prior art program that realizes such added functions.

  FIG. 14 shows a main part of the control of the error information correction apparatus until the correction source is generated by reading the source code in this modification. In this modification, the same processing is performed from step S201 to step S213 shown in FIG. When the correction information and “uncorrectable error information” are output in step S213, a correction source is generated for the correction information (step S214), and the series of processing ends.

  According to the error information correcting apparatus 100A of such a modification, the operator can check the source difference information 117, and if there is no problem in the contents, the operation of correcting the source can be omitted, and the work efficiency can be improved. Can be increased.

  In the embodiment and the modification described above, the output of error information when the compiler detects an error in the source code has been described. However, the present invention is not limited to this. For example, the technique similar to the present invention can be used when outputting error information of a program when the assembler converts assembly language into machine language. In addition, it is natural that the present invention can be similarly applied to correcting errors in a sentence in which various programs are generally described.

It is a block diagram showing the outline | summary of the error information correction apparatus of this Embodiment. It is a flowchart which shows the outline | summary of control of an apparatus until it reads error code with the error information correction apparatus of this Embodiment, and outputs error information. It is explanatory drawing which showed the 1st example which an error generate | occur | produces in this Embodiment. It is explanatory drawing which showed the 2nd example which an error generate | occur | produces in this Embodiment. It is explanatory drawing which showed the 3rd example which an error generate | occur | produces in this Embodiment. It is explanatory drawing which showed the 4th example which an error generate | occur | produces in this Embodiment. It is explanatory drawing which showed the 5th example which an error generate | occur | produces in this Embodiment. It is explanatory drawing which showed the 6th example in which an error generate | occur | produces in this Embodiment. It is explanatory drawing which showed the 7th example in which an error generate | occur | produces in this Embodiment. It is a block diagram showing the error information analysis part of this embodiment concretely. It is a block diagram showing the 1st analysis part more concretely in this embodiment. It is a flowchart showing the mode of the process which the 1st analysis procedure execution part performs in this Embodiment. It is a block diagram showing the structure of the error information correction apparatus in the modification of this invention. It is a flowchart which shows the outline | summary of control of an apparatus until the error information correction apparatus of this Embodiment reads a source code and produces | generates a correction source.

Explanation of symbols

100, 100A error information correction device 101 CPU
102, 102A Memory 105 Source code 106 Source code reading unit 107 Syntax analysis unit 108 Error information analysis unit 109 Source correction information database 111 Operation input unit 112 Display unit 113 Data storage unit 113 ₁ Correctable information storage area 113 ₂ Uncorrectable information Storage area 115 Modified source generation unit 116 Modified source 117 Source difference information 141 Definition data table 142 First analysis procedure execution unit

Claims (6)

Error detection means for detecting errors in the description of the program to be inspected in order along the described lines;
Error cause identification means for analyzing each error detected by the error detection means and determining for each error whether the cause of the error is specific,
Temporary correction means for making a temporary correction such that the error detection means does not detect an error for each cause for the error whose cause is specified by the error cause specifying means;
Temporary correction error output means for outputting the error of the program corrected by the temporary correction means as a group,
An error information output device for a program, comprising: error location information output means for individually indicating locations of errors that cannot be corrected by the temporary correction means in the program to be inspected.   An error correction database storing the correction contents of the error detected by the error detection means for each error is stored, and the error cause identification means searches for errors other than errors that can be corrected by searching in the error correction database. 2. The error information output apparatus according to claim 1, wherein the error information output means is a means for identifying the cause of the error.   2. The operation input means for inputting whether the corrected program output from the temporary correction error output means may remain as a correction content or further correction is required. Error information output device.   2. The error according to claim 1, wherein the program to be inspected is described in source code, and the error detecting means is means for outputting a compile error when converting the source code into machine language code. Information output device. An error detection step for sequentially detecting errors in the description of the program to be inspected along the described lines;
An error cause identifying step for analyzing each error detected in this error detection step and determining whether or not the cause of the error can be identified for each error,
A temporary correction step for performing a temporary correction so that the error detection by the error detection step is not performed according to the cause for the error whose cause is specified by the error cause specifying step;
A temporary correction error output step for outputting the error of the program corrected by the temporary correction step as a group;
An error location information output method for a program, comprising: an error location information output step for individually indicating locations of errors that cannot be corrected by the temporary correction step in the program to be inspected. A computer that corrects errors in the description of the program to be inspected,
An error detection process for detecting errors in the description of the program in order along the described lines;
Analyzing each error detected in this error detection process, an error cause identifying process for determining whether or not the cause of the error can be identified for each error,
For the error whose cause is specified by this error cause specifying process, a temporary correction process for performing a temporary correction so that the error detection process is not detected for each cause, and
Temporary correction error output processing for outputting the error of the program corrected by the temporary correction processing as a group,
An error information output program for a program, wherein an error location information output process for individually indicating locations of errors that cannot be corrected by the temporary correction process in the program to be inspected is executed.

Images