JPH0342727A - System for generating name by pre-compiler - Google Patents

Abstract

PURPOSE:To avoid the coincidence of a name generated by a pre-compiler with a name designated by a user by allowing the pre-compiler to generate the name through the use of characters which can not be used with the user. CONSTITUTION:The source program 1 of a pre-compiler language is the source program whose function is extended by using an SQL language in a COBOL program, for example. The pre-compiler 2 generates the source program 3 of a compiler language by using the characters whose head character is not used in the language concerned as to the name for processing a mentioned part whose function is extended by a library call. A compiler 4 is reorganized so as to recognize the use of the name as to the calling of a library having the name generated by the pre-compiler 2 and the compiler generates a target program 5.

Description

[Detailed Description of the Invention] [Summary] Regarding the name generation method by the precompiler, the precompiler generates names using characters that the user cannot use, and the existing compiler is modified to allow the use of these characters. However, the purpose is to avoid conflicts between the names generated by the precompiler and the names specified by the user, and to prevent translation errors from occurring. Regarding names for processing, the use of this name will be allowed for precompilers that generate names using a character that is not used in a certain language as the first character, and for library calls with names generated by this precompiler. A modified compiler for translating a certain language is provided, and the modified compiler is configured to translate this name and generate a target program.

[Industrial application field]

The present invention relates to a name generation method using a precompiler.

[Prior Art and Problems to be Solved by the Invention] In recent years, as the need for database operations using existing compiler languages has increased, the specifications of existing compiler languages have been expanded. There are two ways to extend language specifications: one is to add functionality to a compiler for a description language, and the other is to create a precompiler that translates into the source language of an existing compiler. The latter is often used for database functions and the like. When this precompiler method is adopted, the name written by the user in the program and the name generated by the precompiler are the same and conflict, resulting in an error when translated by an existing compiler, making it impossible to translate. There was a problem with things happening.

For example, the preprocessor converts the source program shown in Figure 5 (a) as shown in Figure 5 (b), and when the compiler translates it, the name of
A'' should refer to ■, but since the programmer has specified data with the same name in ■, an error will occur during translation.

In the present invention, a precompiler generates a name using characters that the user cannot use, and an existing compiler is modified to allow the use of these characters. The purpose is to avoid collisions between names and translation errors.

[Means to solve problems]

FIG. 1 shows a basic configuration diagram of the present invention.

In Figure 1, the precompiler 2 uses a character that is not used in the language for the first character of the name used to process the function-enhanced description part of a program written in a certain language by calling a library. This is to generate a source program 3 in a compiler language.

The compiler 4 is a compiler that has been modified to allow the use of a name generated by a precompiler for calling a library, etc., and translates the source program 3 in the compiler language into the target program 5.

[Effect]

As shown in FIG. 1, the present invention provides a name for processing a function-enhanced description part in a program (source program 1 of a precompiler language) written in a certain language by the precompiler 2 by calling a library, etc. A source program 3 in a compiler language is generated by using a character that is not used in the language as the first character, and a modified compiler 4 translates library calls with this generated name to generate a target program 5. That's what I do.

Therefore, it is possible to avoid conflicts between the name of the part whose function has been expanded in a program written in a certain language and the name specified by the user, and to prevent errors during translation. .

〔Example〕

Next, the configuration and operation of one embodiment of the present invention will be explained in detail using FIGS. 1 to 4.

In FIG. 1, a source program 1 in a precompiler language is a source program written in a certain language and whose functions are expanded in the program. For example, as shown in FIG. This is a source program that includes program parts whose functions have been expanded using

The precompiler 2 is used to write a part of a program written in a certain language with expanded functions, such as COBOL in Figure 2 (a).
For names used to process extended parts written in the SQL language in a program by library calls, etc., the first character must be a character that is not used in the language concerned (the character marked with ■ in Figure 2 (b)). Using the code following 1 (X"CA")) in the EBCDIC code in Figure 3, create the source program 3 in the compiler language (for example, Figure 2 (B)).
).

Compiler 4 is a compiler that has been modified to allow the use of names generated by the precompiler for library calls that wait for names generated by the precompiler. 5.

Next, the process of converting the source program 1 in the precompiler language into the source program 2 in the compiler language will be explained using FIG.

FIG. 2(a) shows a source program 1 in a precompiler language. Here, the part marked ■ indicates a source program written in the C0BOL language.

The part (2) indicates a functionally expanded part written using the SQL language in the original program written in the COBOL language.

FIG. 2 shows a source program 3 in a compiler language.

The part (2) indicates a parameter area used by the precompiler 2 to call the SQL library (SQL library 7 in FIG. 3) during execution. Here, ■ is C0BO
As a character not used in the L language, the character shown using the ■ next to the alphabetic character "I" in the EBCDIC code in Figure 4 (code
"CA") is added to the beginning of the name.

(2) is a functionally expanded SQL statement converted into a library call using a CALL statement. Here, as shown in the figure, the name of the library call is prefixed with X"CA", and the name is prefixed with a character that is not used in the COB OL language.

This prevents a conflict between the name specified by the user in the COBOL language and the name automatically generated by the precompiler 2, which prefixes the name with "X"CA". In addition, the compiler 4 modifies names starting with the newly added characters that are not used in the COBOL language so that they can be translated. This prevents a conflict between the name automatically assigned by the precompiler 2 and the name assigned by the user during translation by the compiler 4, and avoids a translation error during translation by the compiler 4. Also,
Use characters that cannot be manipulated by the editor.

As described above, the part that stores functions in the source program written in the COBOL language (Figure 2 (a)) is written in the SQL language, and as shown in Figure 2 (b), the precompiler 2 uses the COBOL language. The name generated by the precompiler 2 and the name specified by the user are changed by converting it into a library call with a name starting with an unused character, and then by converting it into the target program 5 by the compiler 4. By avoiding overlap, it is possible to prevent a translation error from occurring during translation by the compiler 4.

FIG. 3 shows an explanatory diagram of the operation at the time of execution according to the present invention.

This is a schematic representation of the situation when the compiler 4 translates the source program 3 in the compiler language shown in FIG. Here, CALL...'' is S in Figure 2 (b) ■.
Corresponding to the execution part of the QL statement, object code 6 C
The ALL statement calls SQL Live Life, performs predetermined processing, and returns to the original state.

FIG. 4 shows the EBCD IC code. Here,■
represents the next position X"CA" of the alphabetic character "I".

By adding this to the beginning of the precompiler 2 and generating the name of the library call, it is possible to avoid the name being the same as the name specified by the user in the C0BOL language, and to avoid a translation error when the compiler 4 translates. This makes it possible to prevent

〔Effect of the invention〕

As explained above, according to the present invention, a configuration is adopted in which the precompiler 2 generates a name using characters that the user cannot use, and modifies the existing compiler 4 to allow the use of these characters. Therefore, precompiler 2
It is possible to prevent the name generated by the user from overlapping the name specified by the user, and to prevent a translation error from occurring during translation by the compiler 4. Furthermore, by making the above characters characters that cannot be manipulated by an editor or the like, it can be made to appear as if no functionality has been added to the existing language from the user's perspective.

[Brief explanation of drawings]

Fig. 1 is a diagram showing the principle configuration of the present invention, Fig. 2 is an explanatory diagram of the operation of the present invention, Fig. 3 is an explanatory diagram of the operation at the time of execution related to the present invention, Fig. 4 is a BBCDTC code, and Fig. 5 is a conventional technique. A diagram explaining the problem is shown. In the figure, 1 represents a precompiler language source program, 2 a precompiler, 3 a compiler language source program, 4 a compiler, and 5 a target program.

Claims (1)

[Claims] In a name generation method by a precompiler, a name for processing by calling a library in a program written in a certain language is generated using a character that is not used in the language as the first character. A precompiler (2) that translates a certain language, which has been modified to allow the use of names generated by this precompiler (2) for library calls with names generated by this precompiler (2).
4), and the modified compiler (4) is configured to translate this name and generate a target program.