JPS62177628A - Processing system for graphic language error - Google Patents

Abstract

PURPOSE:To detect easily the grammatical error of a source program described in a graphic program language out of a compiling error list, by using a labeling means and a source program converting means. CONSTITUTION:An input/output control module 203 judges the compiling command of a source program described in a graphic program language PAD and drives a labeling module 201 and a source program convertion module 202. Then an object program and a compiling error list are produced via both modules 201 and 202 and an existing language compiler 206. The contents of a PAD source program memory 204 consisting of a BOX labeled by the module 203 are read out and displayed or printed in order to detect the grammatical errors out of said error list. Thus the grammatical errors of the source program described in the PAD can be detected easily out of the compiling error list.

Description

Detailed Description of the Invention [Technical Field of the Invention] The present invention relates to a graphical 8-word error handling method used when converting a source program written in a graphical programming language to a source program written in a text format language. Regarding the system.

[Technical background of the invention and its problems]

Graphical program tsmFor example, design a program graphically using PAD, and then write it in C language or FORTRAN.
There are known tools for converting existing language source programs written in text format, such as . FIG. 6 is a flowchart illustrating the procedure for converting a program using such a conversion tool.

First, the programmer designs the PAD program 101 graphically. Next, the conversion tool 102 is used to convert it into an existing source program 103. Next, an object program 105 and a compilation error list 106 are obtained using the existing compiler 104.

Check this error list 106, and if there is an error, press again.
The AD source program 101 is corrected and such processing is repeated until the error disappears.

However, the flowchart shown in FIG. 6 shows the flow that is performed before checking whether the program satisfies the specifications.

However, the error list 106 only points out the grammatical error position in the existing source program 103 by the line number attached to the existing source program 103 (dotted line A in FIG. 6), and the PAD source program 101 Do not point out the above error position (dotted arrow B in Figure 6). Therefore, in order to discover the location of a grammatical error in the PAD source program 101, it is necessary to compare the PAD source program 101 with the existing source program 103 (dotted arrow C in FIG. 6).

[Object of the Invention] The present invention has been made in consideration of the above-mentioned circumstances, and it is possible to easily point out grammatical errors in a source program written in a graphical programming language by compiling (reading) from an error list. The purpose of this invention is to provide a graphical language error handling system that can perform the following tasks.

[Summary of the invention]

In order to achieve the above object, the present invention converts a first source program written in a graphical programming language into a second source program written in a text format language, and then uses a compiler to convert the second source program into a second source program written in a text format language. A graphical language error processing system that obtains an object program and a compilation error list from a program, the system comprising a labeling means for adding labels to all BOXes of a first source program, and associating the added labels with line numbers. means for converting the first source program into a second source program; The present invention provides a graphical language error processing system characterized by displaying images in association with each other.

(Embodiments of the Invention) The present invention will be described in detail below based on illustrated embodiments.

Figure @1 is a block diagram showing the configuration of a graphical language error processing system according to an embodiment of the present invention.

After the CPU 207, which centrally manages all the controls of this system, there is a labeling module 201, a source program conversion module 202, and an input/output management module 203.
, PAD source program memory 204, existing source program memory 205, and existing language compiler 206
is provided. Further, a keyboard 208, a CRT 209, and a printer 210 are connected to the input/output management module 203, and input and output information.

The labeling module 201 is a module for adding labels to all BOXes of the PAD source program, and at the same time, the labels added here are converted by the source program conversion module 202 so that they correspond to the line numbers of the corresponding existing language source program. be done.

The source program conversion module 202 is a module that converts a PAD source program into an existing language source program, and also has a function of converting an added label into a form corresponding to a line number as described above.

The input/output management module 203 has a function of interpreting commands from the keyboard 208 and displaying and printing them on the CRT 209 and printer 210.

The PAD source program memory 204 and the existing language source program memory 205 are memories for storing corresponding source programs. The existing language compiler 206 has a function for creating an object program and a compilation error list from the existing language stored in the existing language source program memory 205. The CPU 207 centrally manages all the modules, memories, and devices described above.

Next, the operation of the system shown in FIG. 1 will be explained.

First, when a compile command for the PAD source program is given from the keyboard 208, the input/output management module 203 judges it and the labeling module 201
, drives the source program conversion module 202. The labeling module 201 adds a label to the BOX retrieved from the PAD source program memory 204,
The data is returned to the memory 204 again.

The source program conversion module 202 converts the above-mentioned label as a line number when converting BOX into an existing language description and converting it into an existing language source program. The converted existing EiH source program is saved in memory 205. Labeling module 20
1 and the source program conversion module 202 operate synchronously.

After the conversion between source programs is completed in this way, the existing language compiler 206 is activated, and the compiler 206 creates an object program and a compilation error list.

This compiler 206 is an existing compiler that has the function of pointing out the error location using the line number of the source program if there is an error in the source program, and the compilation error list is sent to the input/output management module 203 and sent to the CRT 209 or printer 210. Displayed or printed.

Now, to find the error location in the PAD source program from the displayed or printed compilation error list, perform the following operations. The compile error list displays the line number indicating the error position, so if you give a command to display or print the PAD source program from the keyboard 208, the input/output management module 2
03 will judge that. That is, the PAD source program memory 204 consists of the previously labeled BOX.
Read the contents of CRT 209 or Blink 210
Display or print on. Since the line numbers shown in the error list and the labels of the PAD source program are associated with each other as described above, the error location can be identified at a glance.

Next, a more specific explanation will be given using the program conversion forms shown in FIGS. 2 to 5.

First, the source program written in PAD shown in FIG. 2 is converted by the source conversion module 202 into a source program written in an existing language as shown in FIG. 4.

at the same time? As shown in figure A3, labeling module 2
01, a line number 300 and a corresponding label 400 are added to each BOX.

Next, if there is an error in the source program written in the existing language shown in FIG. 4, the compiler 206 points out the error location using a line number 300 as shown in FIG. 5, and outputs this as an error list. for example,!
Since the line number 300 shown in Figure T5 corresponds to the label 400 shown in Figure 3, the error location in the PAD source program can be identified at a glance.

In the above explanation, PAD was used as the program description language before conversion, but this is not limited to PAD, and this book also covers source programs written in all graphical programming languages that do not have line numbers. The invention can be applied.

〔Effect of the invention〕

As explained above, in the present invention, when converting a graphical programming language into a text format language, labels are added to all boxes of the graphical programming language, and the added labels are associated with line numbers. As a result, a graphical language error processing system can be obtained that can easily recognize error locations in a graphical programming language from a compilation error list.

[Brief explanation of drawings]

FIG. 1 is a block diagram showing the configuration of a graphical language error processing system according to an embodiment of the present invention, FIGS. 2 to 5 are program conversion forms used to explain program conversion according to the present invention, and FIGS. The figure is a flowchart for explaining the conventional program conversion procedure. 201... Labeling module, 202... Source program conversion module, 203... Input/output management module, 204... PAD source program memory, 205... Existing language source program memory, 2
06... Existing language compiler. Applicant's representative Mr. Sato Figure 1 First, 10 5UBROUTINE 5aODD20
READ 01 30 CAu GETSYM(X) 40 1F (MOD(X, 2), EQ, 1) 50
THEN FLG='YES'60 ELSE
FLG = N6 “6 Figure 4 Figure 5

Claims (1)

[Claims] After converting a first source program written in a graphical programming language into a second source program written in a text format language, a compiler is used to extract an object program and a compilation error list from the second source program. a graphical language error processing system to obtain a graphical language error processing system, further comprising a labeling means for adding labels to all BOXes of the first source program, and a labeling means for attaching labels to all BOXes of the first source program; a means for converting the second source program into a program, and displaying errors in the second source program displayed by line numbers in the compile error list in association with labels added to the BOX of the first source program. Features a graphical language error handling system.