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

Make it more obvious what's boilerplate and what's code being tested #228

Open
axtens opened this issue Jul 31, 2022 · 2 comments
Open

Make it more obvious what's boilerplate and what's code being tested #228

axtens opened this issue Jul 31, 2022 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@axtens
Copy link

axtens commented Jul 31, 2022

Currently line numbers are not being used in columns 1-6. Can the code being tested have line numbers matching the line in the original, viz:

       boilerplate code 
000001 identification division.
000002 program-id. code-being-tested.
       more boilerplate code

Thus when gnucobol complains, the programmer can open the CC##*.cob file at the point of error and see the line number of the code being tested and be able to go back to the source at the matching line.

@dakaa16
Copy link
Collaborator

dakaa16 commented Aug 8, 2022

That would be a great addition. I'll implement it when I've got the time. Currently you can have Cobol Check insert start- and end tags for injected code, in the form of comments. You can add it to the configuration file like this

@dakaa16 dakaa16 self-assigned this Aug 8, 2022
@dakaa16 dakaa16 added the enhancement New feature or request label Aug 8, 2022
@axtens
Copy link
Author

axtens commented Mar 21, 2024

Bump. Here we are almost two years later. Do you have any time yet?

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

No branches or pull requests

2 participants