Releases: opensourcecobol/opensourcecobol4j
Releases · opensourcecobol/opensourcecobol4j
v1.1.12
Add
- Implemented new file locking and record locking for INDEXED files.
- Add a new sub command
migrate
forcobj-idx
.- With this command, you can convert an old version of an INDEXED file to a new version compatible with the latest opensource COBOL 4J.
- Add a new sub command
unlock
forcobj-idx
.- With this command, you can unlock all record locks and file locks on an INDEXED file.
- Add documentation of locking for INDEXED files.
v1.1.11
v1.1.10
v1.1.9
Add
- Add a sub command create for cobj-idx. (#648)
cobj-idx create
creates a new indexed file.
Fix
- Handle non-ASCII characters in EXTERNAL items and EXTERNAL file names correctly. (#624)
- Show error messages if unimplemented subroutines are used. (#628)
- Fix non-ASCII characters in external items and external file descriptors. (#629)
- The older version does not convert
-
in EXTERNAL items and EXTERNAL file names into another valid character in Java. - The older version converts
BC
in EXTERNAL file names into invalid characters.
- The older version does not convert
v1.1.8-hotfix1
Fix
- Fix code generations for some WRITE statements.
- Older versions of the compiler converts some WRITE statements into invalid Java code.
- Fix the compiler to handle source code with UTF-8 encoded half-width Katakana characters correctly.
v1.1.8
Fix
- Fix a bug of duplicate record keys of indexed files
v1.1.7-hotfix1
Fix
- Fix bugs related to UTF-8
- With older versions, DISPLAY statements output invalid UTF-8 data when the arguments are sub items of group fields.
- With older versions, initilizing data with VALUE clauses fails in some cases.
v1.1.7
Add
- Implement the environment variable
COB_TERMINAL_ENCODING
.- If the value of
COB_TERMINAL_ENCODING
isUTF-8
, the DISPLAY statement outputs data after converting it to UTF-8. Otherwise, it outputs raw data (typically encoded in Shift JIS). - If the value of
COB_TERMINAL_ENCODING
isUTF-8
, the ACCEPT statement processes input data as UTF-8 encoded. Otherwise, it processes input data as Shift JIS encoded.
- If the value of
- Fix the UTF-8 compatible compiler to recognize that the size of multibyte characters in COBOL source code as 2 bytes instead of 3 bytes.
- This change allows users to write more multibyte characters on each line of the COBOL source code.
v1.1.6
Add
- Compile UTF-8 Source Code
- The latest version of cobj is now able to accept UTF-8 encoded COBOL and generate UTF-8 encoded Java.
- See documentation to install the UTF-8 compatible compiler.
v1.1.5
Add
- String literals containing SJIS characters are remained as they are, not being converted into byte arrays.
- The older versions convert string literals containing SJIS characters into byte arrays with hexdecimal integers.
- Older versions convert
"日本語"
intoCobolUtil.toBytes((byte)0x93, (byte)0xfa, (byte)0x96, (byte)0x7b, (byte)0x8c, (byte)0xea)
. - Latest version converts
"日本語"
intoCobolUtil.stringToBytes("日本語")
.
- Older versions convert
- The older versions convert string literals containing SJIS characters into byte arrays with hexdecimal integers.
Fix
- Fix comparisons of COMP data.
- With older versions, comparisons of COMP data are invalid in some cases.