TypeCobol
TypeCobol copied to clipboard
TypeCobol is an Incremental Cobol parser for IBM Enterprise Cobol 6 for zOS syntax. TypeCobol is also an extension of Cobol 85 language which can then be converted to Cobol85.
**What is the current problem** Implement new check: `The specified"USAGE"was different from the "USAGE" specified at the group level. The group "USAGE" was assumed for this item.` Cobol code to...
**What is the current problem** **FOLLOWING OF #1459** Support set to false in DFA Cobol code to illustrate. ```cobol TODO ``` **Technical** Will be edited by a team member. Implementation...
**Describe the bug** We currently consider a token to be the target of a replacement even if it only partially matches. This happens for `PartialCobolWord `and `PictureCharacterString`. This issue only...
In some incremental parsing scenarios, diagnostics created during compiler directive processing are duplicated. `ProcessingDiagnostics` are created: - to signal errors that occur during EI-Legacy suffixing - to signal errors for...
**Describe the bug** Following #2467, the reparsing of SPECIAL-NAMES doesn't works at least for `currency sign is`. **To Reproduce** See test [Program](https://github.com/TypeCobolTeam/TypeCobol/blob/develop/TypeCobol.Test/Parser/Programs/Cobol85/Program.pgm) executed with test `RewriteLineByLineInReverseOrder`. **Expected behavior** Correct reparsing...
For issue #704 we should create an error only if the code will be generated for Cobol 85. Currently we only generated code for Cobol 85 but if one day...
# Describe the bug Generatlization of #2471. IBM Compiler check characters allowed in replace clause. See "Chapter 1. Characters" page 3 of IBM PDF "Enterprise COBOL for z/OS 6.3 Language...
Following #1515, it appears that FunctionCaller interface is not used anymore. Current implementations are Move and ProcedureStyleCall but Move is never used as FunctionCaller and ProcedureStyleCall is usied directly.
According to _IBM Enterprise Cobol 5.1 for zOS - Language Reference_ p109, the entries of a program configuration section must be in the following order : source-computer-paragraph, object-computer-paragraph, special-names-paragraph, repository-paragraph....
**Describe the bug** Following #2190 and PR #2465, the ScanState used by TokensLinesIterator in AutoReplacePartialWordsTokensDocument is not always correct. This TokensLinesIterator must use the ScanStateTracker to recalculate the correct ScanState....