TypeCobol icon indicating copy to clipboard operation
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.

Results 223 TypeCobol issues
Sort by recently updated
recently updated
newest added

Using the following sample derived from the one at ![image](https://github.com/TypeCobolTeam/TypeCobol/assets/19149269/a484697a-b1c1-496c-b645-fe80d3c88517) produces a CFG that is not extended correctly, there will still groups not extended. ```cobol IDENTIFICATION DIVISION. PROGRAM-ID. EXITSEC0. DATA...

**What is the problem ?** The scanner uses the `MulitlineScanState.EncodingForAlphanumericLiterals` property to get the string value of alphanumeric literals described using the hexadecimal notation. However this property gets its value...

The class `ExtensionManager` uses `Assembly.LoadFrom` to load extensions identified by their assembly file path. This method may lead to duplicate assemblies loaded in same context. A better option would be...

In current state, the build order is not consistent across build tools. It works fine inside Visual Studio but not necessarily on every CI: here on GitHub Actions we have...

Child of #2668. This is a minimalistic approach to LS exception tracking : - in `TypeCobolServerHost`, as soon as the `TypeCobolServer` instance is available , add a new `ILogger`. -...

To improve monitoring of our LanguageServer, we have to introduce some telemetry events for server exceptions. This issues encompasses multiple goals : - introduce support for `telemetry/event` LSP method -...

**Describe the bug** For instance, a diagnostic is created because a VALUE assigned to a data is too big compared to the data declaration. The diagnostic mentions the value itself....

Bug
Cobol
User Visible

Our implementation of LSP is quite old now and more importantly is embedded instead of relying on a well-known externally-provided package. Migrating to `Microsoft.VisualStudio.LanguageServer.Protocol` NuGet package is the target however...

**Describe the bug** Following #2083, it appears that the syntax is correctly supported but the semantics of abbreviated expressions is wrong. See the code example. **To Reproduce** ```cobol IDENTIFICATION DIVISION....

Bug
Cobol
To Analyze