You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The COBOL Language Server does not correctly handle condition expressions on compilation variables in boolean format compared with the constant b'0' or b'1', which subsequently triggers parse errors at the global level and emitting false syntax errors.
Problems also on parsing the >>evaluate directive:
The text was updated successfully, but these errors were encountered:
I haven't tested it but I think that if the management of conditional compilation does not work at the Language Server level, and this leads to poor or false detection of the COPYBOOKs actually used by the program during compilation, this must have a impact on the IBM User Build function (call to DBB-zAppbuild): copybooks will be missing (transfer from local to remote system) when compiling User Build.
In general, the poor management of conditional compilation by the COBOL Language Server causes us many problems and makes most of the features specific to Z Open Editor unusable (any syntax error disables many features in ZOE).
Perhaps you should consider no longer managing conditional compilations and considering that all the source lines are part of the program (management by excess, but at least the "necessary" is managed, in the absence of the "sufficient"), or provide an option to allow disabling conditional compilation support in the COBOL Language Server.
In any case, we want substantive and rapid action on the problems related to the management of conditional compilation in the COBOL Language Server because we have now switched to intensive use mode of Z Open Editor and these problems are becoming critical for us.
Development environment used
Problem Description
The COBOL Language Server does not correctly handle condition expressions on compilation variables in boolean format compared with the constant b'0' or b'1', which subsequently triggers parse errors at the global level and emitting false syntax errors.
Problems also on parsing the >>evaluate directive:
The text was updated successfully, but these errors were encountered: