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

See #995 `namespace` and `using` clause : - Type and procedure can now be qualified with a namespace - Search of types and procedure without namespace qualification must use `using`...

Enhancement
Functions
Types
User Visible

```cobol 01 TOTO typedef strict pic X. 01 TITI typedef strict type TOTO. *> this should be working ```

Bug
Types
User Visible

The case is as following : We have one main Program like this : ```COBOL MAIN PROGRAM 01 myVar TYPE Dep1::DataType [...] MOVE myVar::Child1::DataChild::Branch TO ... ``` ```COBOL DEP1 PROGRAM...

Bug
TypeCobol
Types
::
User Visible

See #995 which was the proposal for a refactoring of visibility and namespace introduction. See (TODO create issue) for the meeting about this proposal. Issue #1081 Public/Private visibility refactoring should...

Enhancement
Functions
Types
User Visible
Namespace & Visibility

We are facing a problem does not allow parser to seek for type inside a type contains in a dependencies file. What we need to do today, is to qualify...

Bug
TypeCobol
Types
User Visible

New features for functions and procedures: - [ ] **TCRFUN_TCFUNC_WHERE_COBOL85FUNC_** A custom function can be called as part of any statement where an COBOL 85 intrinsic function call would be...

Enhancement
TypeCobol
To Analyze
Functions
User Visible

For function invocations, the codegen always generates in the corresponding generated `CALL` statement the same return value holder variable for a given function call : **-RESULT**. Two problem with this...

Bug
To Fix
Functions
User Visible

Change rule **TCRFUN_LIBRARY_PROCEDURE_NO_USING** described here: https://github.com/TypeCobolTeam/TypeCobol/wiki/TypeCobolFunctionsSyntax A program which contains public procedure should be able to have input/output paramters in its `procedure division using` clause. Also update page https://github.com/TypeCobolTeam/TypeCobol/wiki/TypeCobolFunctionsSyntax and...

Enhancement
TypeCobol
Codegen
Functions
User Visible

```cobol TODO Complete code here ``` Also, do we need to always generate a working/local storage? Because some simple procedure don't always need a working/local storage.

Enhancement
Cobol
Codegen
User Visible