minor issues in the manpage (and possibly implementation)
- it partially says COBOL, but in many places Cobol - in any case the same variant should be used (I'd personally use all-uppercase as COBOL is an acronym)
-
-I -/usr/local/include:include
seems to be a typo, there is likely no hyphen before the path - in the text explaining above: shouldn't "include" be used from the working directory? Is that really used form the source file?
- 'supports the following USAGE “IS” clauses' - the quotes around the optional IS looks... weird.
5- data-types - isn't COMP-1 identical to standard
FLOAT-SHORT
, COMP-2 toFLOAT-LONG
?`In this case you may want to add that to the parser (if missing) + docs. - is
COMP-5
always little-endian? It should be "native". - " For the BINARY-type, aliaes, UNSIGNED is the default." - this would conflict with ISO which defines those (the manpage is referencing "other implementations" instead) to be - per default - SIGNED.
- PACKED-DECIMAL is really important, one of the reasons is that SQL preparsers often only support those for any decimal numeric item.
- History: You may add Otterkit to the list; but it does not yet pass NC (you could change the text to
Besides gcobol, the only other active free COBOL compiler project that passes the NC module as of 2022 is GnuCOBOL (https://gnucobol.sourceforge.io/).
[note: that URL should definitely stay on one line, my reader makes a link to "https://gnu" out of it because of the line overflow!]
Edited by Simon Sobisch