Nicolas Berthier

Support collating sequence for indexed file keys of alphanumeric class

Check for incompatible data only when a receiver is of category numeric in MOVE or SET

Hi Ralph, Very interesting project indeed. The missing element was collating sequence. For instance an EBCDIC "123" must collate after an EBCDIC "ABC". I converted the EBCDIC "123" to an ASCII "123" Hence I depend on the "collating sequence EBCDIC " to evaluate comparative expressions as if implemented by Micro Focus CHARSET "EBCDIC". That is X'414243" to be less that X'313233' ("ABC" < "123"). I can confirm this is exactly what the EBCDIC-related command-line options are doing.

Hi Ralph, Indeed, I think that the combination of flags -fsign=ebcdic -fdefault-colseq=ebcdic -febcdic-table=ebcdic500_latin1 should make the specification of PROGRAM COLLATING SEQUENCE … EBCDIC redundant. Note: I think even with these flags, the files manipulated by the programs compiled using GnuCOBOL should be ASCII and not EBCDIC; but that may be what you expect.

Retrieve archive of NIST test suite from sourceforge instead of from an out-dated URL

`-lreadline` may be missing when linking `cobfile` in `trunk`

Hi @vedant23, First of all many thanks for contributing via this proposal. Overall this seems a well planned and important project (in particular the first two deliverables, and the one on stubs, the other ones appearing less detailed to me). I've made some suggestions on the document, mostly to improve presentation for people that might not know GnuCOBOL or its status so far. Furthermore, I am not familiar with typical proposals for GSoC, but I would also have expected a list of identified potential...

Indeed, I've bisected the correction down to a change in [r4467] (that followed works "Handle multi VALUES with OCCURS" in [r4459], that exhibits the bug).