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
For the LSP that shouldn't make such a big difference for now (you may add a dialect option gcc-cobol / gcc-cobol-mf / gcc-cobol-ibm or similar later, which has a different set of reserved words - but using the gc ones matching the dialect should be fine.
For the extension itself - one could either use the GnuCOBOL build - but defining the cobc binary as gcobc (a wrapper around gcobol), or actually provide a template for gcobol compilation. The coverage option would be identical --coverage and displaying the result should still be identical.
The pattern matchers for the diagnostic are likely different (sarif format or similar would also be possible - gcobol now provides clear ranges, including columns), but adding a gcc one (that's in general) or, to prevent name conflicts, gcobol one shouldn't be hard.
Debugging could be explicit defined as "for now only GnuCOBOL 3.2+ is supported", and if the debugging extension would be split out it could be possible to just use a common debug extension like native-debug (with a most updated GDB containing the necessary parts, of course).
The text was updated successfully, but these errors were encountered:
For the LSP that shouldn't make such a big difference for now (you may add a dialect option gcc-cobol / gcc-cobol-mf / gcc-cobol-ibm or similar later, which has a different set of reserved words - but using the gc ones matching the dialect should be fine.
For the extension itself - one could either use the GnuCOBOL build - but defining the cobc binary as gcobc (a wrapper around gcobol), or actually provide a template for gcobol compilation. The coverage option would be identical
--coverage
and displaying the result should still be identical.The pattern matchers for the diagnostic are likely different (sarif format or similar would also be possible - gcobol now provides clear ranges, including columns), but adding a gcc one (that's in general) or, to prevent name conflicts, gcobol one shouldn't be hard.
Debugging could be explicit defined as "for now only GnuCOBOL 3.2+ is supported", and if the debugging extension would be split out it could be possible to just use a common debug extension like native-debug (with a most updated GDB containing the necessary parts, of course).
The text was updated successfully, but these errors were encountered: