Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support gcobol #405

Open
GitMensch opened this issue Feb 14, 2025 · 0 comments
Open

support gcobol #405

GitMensch opened this issue Feb 14, 2025 · 0 comments

Comments

@GitMensch
Copy link
Contributor

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant