JP2010224656A - Source code generation device, program and source code generation method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce the load in development of software for processing a record contained in a file of a character code expressed by two full-width two-bytes or one half-width one-byte with a character code expressed by the same byte number for both full width and half width. <P>SOLUTION: The device includes a generation means for setting, based on file layout information showing the layout of a file composed of a character string record including a plurality of items each composed of a character code of one or two or more byte arrays, setting information to a code converter according to the type corresponding to each item of the character string record, and automatically generating a source code related to conversion of the character code of the character string record. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a source code generation device, a program, and a source code generation method.

  In a Japanese-speaking personal computer, a character code represented by two-byte full-width and one-byte single-byte represented by Shift_JIS is generally used as a character code for representing kanji. However, as the globalization of applications has progressed recently, character codes for dealing with a plurality of linguistic areas have been arranged, and instead of treating single-byte characters and single-byte characters as one character, a character code that represents one character in n bytes For example, Unicode is increasing. In particular, personal computers (hereinafter also referred to as PCs) have increasingly used such character codes.

  On the other hand, in a legacy system linked with a host computer or the like, a character string area can be easily estimated, and character codes expressed by 2 full-byte characters and 1 single-byte character remain persistently. In a programming language that handles a fixed-length data structure typified by COBOL, the data size is assigned in bytes. For this reason, Shift_JIS, which has a fixed length and is easy to design, is adopted in the COBOL of the PC.

In COBOL, when a file is handled, a record representing a character string may be handled. This is called a SAM file. In the SAM file, corresponding record definition information is recorded by being linked in byte units. For this reason, when handling a SAM file in a language other than COBOL, it is necessary to cut out, link, etc. for each item. Here, FIG. 1 is a diagram showing an example of a record definition, Shift_JIS code record data, and Unicode record data. FIG. 1 shows the case of COBOL as an example of the record definition.
In the Shift_JIS code system, since the byte image in the record definition matches the internal representation of the character string, it is easy to cut out. However, as shown in FIG. 1, in the case of Unicode, there is a discrepancy between the byte image of the record definition (COBOL record definition) and the internal representation of the character string due to the difference in the number of bytes between full-width characters and half-width characters.

In FIG. 1, for example, the Shift_JIS code used in the SAM file as described above is represented by 2 bytes of full-width characters and 1 byte of half-width characters. Therefore, the character string “A” arranged in ITEM01 is expressed as, for example, A = 82A0, A = 41, and the like. On the other hand, within an application whose internal representation is Unicode, whether it is full-width or half-width, it is treated as 2 bytes per character. Therefore, the character string “A” arranged in ITEM01 is expressed as, for example, A = 3042, A = 0041, and the like.
In this way, an area represented by 3 bytes in Shift_JIS is represented by 4 bytes in Unicode. The longer the string, the greater the gap.
In particular, when a record in which full-width data and half-width data are mixed is used in Unicode, processing for matching with the byte image of the record definition is required.

JP-A-5-298065

FIG. 2 is a diagram illustrating an example of processing that is required when a Unicode application reads a record written in a Shift_JIS code file into a memory and performs processing (original processing). In the example of FIG. 2, the record α includes items A, B, and C, and includes a reserve (FILLER) between the items B and C.
As shown in FIG. 2, conventionally, for example, the PC reads each item from the SAM file of the Shift_JIS code before performing an original process such as reading or writing data from the item in Unicode. It was necessary to cut out and convert the character code from Shift_JIS code to Unicode, and to associate the byte image of the record definition with the data (item) converted to Unicode and store it in the memory. Further, when the PC returns the record to the SAM file after performing the original processing, it is necessary to convert the Unicode to the Shift_JIS code, combine the items, and write the data to the SAM file. These processes such as cutout, conversion, and combination are processes accompanying the original process. However, the amount of coding for realizing the accompanying processing increases in proportion to the type of record, the number of items, and the like. For this reason, it has become one of the factors that deteriorate the development efficiency of applications (software) and one of the factors that deteriorates maintenance efficiency.

  Also, as shown in FIG. 1, in the conventional method, for example, when a spare is included between items of a record, coding for processing to eliminate or add this spare is also necessary. In addition, the conventional method also requires coding for processing that handles group items described later.

  The present invention has been made in view of such a problem, and software for processing a record included in a character code file expressed by 2 full-width characters and 1 single-byte character by using a character code expressing the same number of bytes. The purpose is to reduce the development load.

  Therefore, the present invention corresponds to the item of the character string record based on the file layout information indicating the layout of the file composed of the character string record including a plurality of items composed of one or more byte array character codes. A setting unit configured to automatically generate a source code related to conversion of a character code of the character string record by setting setting information in the code converter for each type and combining the code converter for each type And

  With this configuration, a source code related to conversion of the character code of the character string record is automatically generated based on the file layout information. Software developers who process records contained in character code files that are represented by 2 bytes and 1 byte can be processed using the same number of bytes. Create the software. Therefore, it is possible to reduce the development load of software for processing records included in a character code file expressed by 2 bytes and 1 byte by using the same number of bytes.

  The generation unit corresponds to, for example, a conversion device described later. The file layout information corresponds to, for example, a record definition described later.

  Further, the present invention may be a program and a source code generation method.

  According to the present invention, it is possible to reduce the load of software development for processing records included in a character code file expressed by 2 full-byte and 1 single-byte characters by using a character code expressed by the same number of bytes. it can.

It is a figure which shows an example of a record definition, the record data of Shift_JIS code, and the record data of Unicode. It is a figure which shows an example of the process required when the application of Unicode reads the record described in the file of the Shift_JIS code | cord | chord in the past, and performs a process (original process). It is a figure which shows an example of the system configuration | structure of the system of this embodiment. 2 is a diagram illustrating an example of a hardware configuration of a record source program code generation device 2. FIG. It is a sequence diagram of an example concerning a record source program code generation process. It is a class diagram which shows an example of the function of the system of this embodiment. It is a figure which shows an example of a code converter. It is a figure which shows an example of a group item converter. It is a figure which shows an example of a 9-type converter. It is a figure which shows an example of an X-type converter. It is a figure which shows an example of FILLER. It is a figure which shows an example of a S9 type | mold converter. FIG. 3 is a diagram for explaining this embodiment in comparison with FIG. 2.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

FIG. 3 is a diagram illustrating an example of a system configuration of the system according to the present embodiment. As shown in FIG. 3, in the system, a record definition repository device 1, a record source program code generation device 2, a developer device 3, and a client device 4 are connected via a network 5. In FIG. 3, the client device 4 is described as being connected to the network 5, but the client device 4 may not be connected to the network 5.
The record definition repository apparatus 1 stores a plurality of record definitions as shown in FIG. The record source program code generation device 2 acquires the record definition from the record definition repository device 1 based on the generation request from the developer device 3, and includes it in the SAM file shown in FIG. 1 based on the acquired record definition. Setting information is set in the code converter for each type corresponding to the record item to be recorded, and the record code for converting the character code of the record is automatically generated by combining the code converter for each type.

The developer device 3 acquires the record source program code automatically generated by the record source program code generation device 2. The developer operates the developer device 3 and uses the automatically generated record source program code to record the records included in the character code file represented by 2 bytes and 1 byte as the same number of bytes. The software (hereinafter simply referred to as software) to be processed with the character code expressed in (1) is created.
As will be described in detail with reference to FIGS. 7 to 12 described later, for example, when the code converter is instructed to write data from software, it converts Unicode data into Shift_JIS data and sets information. The data is written at the position of the record set in. When the code converter for each type is instructed to read data from the software, it reads Shift_JIS data from the position of the record set in the setting information and converts it to Unicode data.

  The software created by the developer device 3 and the code converter for each type are distributed to the client device 4 via a network or a storage medium, and executed by the client device 4 of Unicode, for example.

FIG. 4 is a diagram illustrating an example of a hardware configuration of the record source program code generation device 2.
As shown in FIG. 4, the record source program code generation device 2 includes a CPU 11 as a hardware configuration. The CPU 11 realizes the function of the conversion device by performing processing based on the program stored in the storage device 13.
An input device 12, a storage device 13, and a display device 14 are connected to the CPU 11 via the bus 10. The storage device 13 includes, for example, a ROM, a RAM, a hard disk device, and the like, and stores data used in processing based on the program in addition to the above-described programs. The display device 14 is, for example, a display that displays information. The input device 12 is, for example, an operation key for inputting information.
The hardware configuration of the record definition repository device 1, developer device 3, and client device 4 is the same as that of the record source program code generation device 2 shown in FIG.
The input device 12 and the display device 14 are not essential components of the record source program code generation device 2.

FIG. 5 is a sequence diagram illustrating an example of the record source program code generation process.
In SQ 10, the developer device 3 transmits a record source program code generation request including identification information for identifying the SAM file to the record source program code generator 2.
The record source program code generation device 2 holds association information for associating the SAM file with the record definition in the storage device 13 or the like, and based on the identification information of the SAM file included in the record source program code generation request, A record definition corresponding to the SAM file is specified.
The record source program code generation device 2 transmits a search request including identification information for identifying the identified record definition to the record definition repository device 1, and obtains the record definition identified by the identification information to the record definition repository device 1. Request.

  The developer apparatus 3 may transmit a record source program code generation request including identification information for identifying the record definition to the record source program code generation apparatus 2. In such a case, the record source program code generation device 2 transmits a search request including identification information for identifying the record definition included in the record source program code generation request to the record definition repository device 1 and is identified by the identification information. The record definition repository apparatus 1 is requested to acquire the record definition to be executed.

FIG. 6 is a class diagram showing an example of the functions of the system of this embodiment.
As shown in FIG. 6, the system of the present embodiment includes a conversion device and a code converter as functions. The code converter includes a group item converter, a type 9 converter, an S9 type converter, and an X type converter. The conversion device is a program executed by the record source program code generation device 2. The code converter is a program executed by the client device 4 or the like. Further, the converter may include a converter other than the converter described above.

Based on the record definition, the conversion device is a code converter for each type corresponding to the item of the record included in the SAM file (for example, a group item converter, a 9-type converter, an S9-type converter, an X-type converter, etc. ) In the setting information (for example, ID, data, start position, length, integer length, decimal length, etc. shown in FIG. 7 to be described later), and by combining the code converters by type, A record source program code related to character code conversion is automatically generated.
In the following, the code converters shown in FIGS. 7 to 12 show examples of combinations of setting information and code converters set by the conversion device based on the record definition shown in FIG.

FIG. 7 is a diagram illustrating an example of a code converter. The code converter corresponds to a record in the COBOL grammar. The code converter holds an element for referring to the data part.
FIG. 8 is a diagram illustrating an example of a group item converter. The group item converter corresponds to a group item in the COBOL grammar. The group item converter holds elements for referring to the data part and can collect data.
FIG. 9 is a diagram illustrating an example of a 9-type converter. The 9-type converter corresponds to 9 types in the COBOL grammar. The 9-type converter holds a numerical value as an internal representation as a Shift_JIS character string, and converts the numerical value and the Shift_JIS character string at the time of input / output. The 9-type converter manages the data area as a fixed point expressed by an integer part and a decimal part, and performs rounding for an input exceeding the precision.

FIG. 10 is a diagram illustrating an example of an X-type converter. The X-type converter corresponds to the X type in the COBOL grammar. The X-type converter holds a numerical value as an internal representation as a Shift_JIS character code, and converts an object processing system code (for example, Unicode) and a Shift_JIS code at the time of input / output.
FIG. 11 is a diagram illustrating an example of FILLER. There is no converter corresponding to FILLER. An area not managed by a converter that expresses a direct value such as a 9-type converter, an S9-type converter, or an X-type converter is FILLER.
FIG. 12 is a diagram illustrating an example of the S9 type converter. The S9 type converter corresponds to the S9 type in the COBOL grammar. The S9 type converter holds a numerical value as a shift_JIS code character string as an internal representation, and performs conversion between the numerical value and the Shift_JIS character string at the time of input / output. The S9 type converter manages the data area as a fixed point expressed by an integer part and a decimal part, and rounds an input exceeding the precision. The difference between the S9 type converter and the 9 type converter is that the S9 type converter can manage the sign, and in the case of a negative number, it is expressed by adding 0x40.

FIG. 13 is a diagram for explaining this embodiment in comparison with FIG. As shown in FIG. 13, in the present embodiment, the conversion device automatically generates the source code related to the conversion based on the record definition, so that individual coding by the developer is unnecessary. In addition, since no coding is required, there is no problem even if the number of records or items increases. Also, developers do not need to consider spare parts and do not need to code to handle group items.
According to the present embodiment, for example, the character string of the Shift_JIS code is stored in the memory of the client device 4 whose internal representation is Unicode. Each code converter is called from an application or the like, and sequentially executes processing related to conversion each time data is written or read.

As described above, according to the present embodiment, as described above, the development of software that processes records included in a character code file expressed by 2 full-width characters and 1 single-byte character by a character code expressing both full-width and half-width characters by the same number of bytes. Can reduce the load.
In addition, according to the present embodiment, when a developer develops software using automatically generated source code, for example, when performing implementation (coding) instructing the code converter to write data. In addition, for example, when an instruction to write wrong type data or the like is given, an error is displayed at the time of compilation or the like, so that correction can be performed. On the other hand, in the case of the conventional example as shown in FIG. 2, no error is displayed at the time of compilation or the like even if the coding is incorrect as described above.

  The preferred embodiments of the present invention have been described in detail above, but the present invention is not limited to such specific embodiments, and various modifications can be made within the scope of the gist of the present invention described in the claims.・ Change is possible.

2 record source program code generator 11 CPU
12 Input device 13 Storage device 14 Display device

Claims (7)

  Code conversion according to type corresponding to the item of the character string record based on the file layout information indicating the layout of the file composed of the character string record including a plurality of items composed of one or more byte array character codes A source code generation apparatus comprising: generation means for setting setting information in a device and automatically generating a source code relating to conversion of a character code of the character string record.   The generating means sets the setting information in a code converter for each type corresponding to the item of the character string record based on the file layout information, and combines the code converter for each type to combine the character string. 2. The source code generation apparatus according to claim 1, wherein a source code relating to conversion of a character code of the record is automatically generated. Receiving means for receiving a source code generation request including identification information for identifying the file;
Search means for searching file layout information indicating a layout of the file from a storage device based on the file identified by the identification information included in the source code generation request received by the receiving means;
Further comprising
The generation unit automatically generates a source code related to conversion of a character code of a record constituting the file, based on the file layout information acquired as a result of the search by the search unit. The source code generation device according to 2.   The generation means, based on the file layout information, in the code converter by type, reference information for referring to the character string record, the start position of the byte array related to the item, the length of the byte array related to the item The source code generation apparatus according to any one of claims 1 to 3, wherein the length is set as setting information.   The source code generation apparatus according to claim 4, wherein the character string record includes a spare part. Computer
Code conversion according to type corresponding to the item of the character string record, based on file layout information indicating the layout of a file composed of a character string record including a plurality of items composed of one or more byte array character codes A program characterized in that setting information is set in a device and functions as a generating means for automatically generating a source code relating to conversion of a character code of the character string record. A source code generation method in a source code generation device,
Code conversion according to type corresponding to the item of the character string record, based on file layout information indicating the layout of a file composed of a character string record including a plurality of items composed of one or more byte array character codes A source code generation method comprising: a generation step of setting setting information in a device and automatically generating a source code related to conversion of a character code of the character string record.

Images