| Key | Issue | Reported | Fixed | Disposition | Status | |
|---|---|---|---|---|---|---|
| COBOL-2 | COBOL Language Mapping Section: 1.2.1.2 | COBOL 1.0 | open | |||
| COBOL-1 | anomaly in that unsigned integers are mapped to signed integers | COBOL 1.0 | open | |||
| COBOL-3 | Mapping of short and long | COBOL 1.0 | open |
"4. If the identifier is greater than 30 characters, then truncate right to 30 characters."
After this step there might be a hyphen at the end of the identifier. This should be truncated, too.
While skimming the CORBA->COBOL mapping of IDL constructs, I noticed an
anomaly in that unsigned integers are mapped to signed integers:
> IDL Name
> COBOL Representation Integer Range COBOL Typedef
>
> unsigned short
> PIC S9(05) BINARY 0 to 2^16 CORBA-unsigned-short
> unsigned long
> PIC S9(10) BINARY 0 to 2^32 CORBA-unsigned-long
> unsigned long long
> PIC S9(18) BINARY 18 numerics CORBA-unsigned-longlong
> enum
> PIC S9(10) BINARY CORBA-enum
>
> 1.4.1 Basic Integer Types
>
> The mapping of long long,
> and unsigned long long
> was made to PIC S9(18)
> and PIC 9(18).
Presumably the statement of section 1.4.1 is the correct one?
The integer ranges given are wrong, correct would be -2^15 to 2^15 -1 and -2^31 to 2^31 -1.
The COBOL Representation for short should be PIC S9(4) BINARY (which is 2 bytes) and for long PIC S9(10) BINARY (which is 4 bytes).