Profile wanted: Micro Focus (Rocket) COBOL
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Read docs/adding-a-compiler.md, especially the verification steps and step 5, then inspect the built-in microfocus profile. Run the listed cobalto test commands with Visual COBOL, Enterprise Developer or COBOL Server, adjusting the profile as needed; check the cob command line, LINE SEQUENTIAL results output, and compiler directives affecting arithmetic and binary field sizes. Done means reporting the results and, if successful, submitting a pull request that marks the profile verified.
Written by the indexing model from the issue text.
Description
The built-in microfocus profile is a template that has never been run:
{
"description": "Micro Focus / Rocket Visual COBOL. NOT verified: template.",
"results_org": "LINE SEQUENTIAL",
"results_format": "lines",
"results_path": "build/cblt-results.txt",
"compile": "cob -x -I {lib} {incl} -o {exe} {driver} {lib}/CBLTLIB.cbl {tests} {sources}",
"run": "{exe}"
}
The gnucobol-mf profile runs GnuCOBOL with -std=mf. It approximates Micro Focus rules, but it is not the Micro Focus compiler.
What is needed
Someone with Visual COBOL, Enterprise Developer or COBOL Server who can run the example project with that profile, adjusted where needed:
cobalto test --profile microfocus --filter TSTDISC --no-run -v
cobalto test --profile microfocus --filter TSTDISC -v
cobalto test --profile microfocus --coverage
The steps, and what "verified" means, are in Adding a compiler. Worth checking on the way: the cob command line, whether LINE SEQUENTIAL works for the results file, and which compiler directives change arithmetic or the size of binary fields, since those explain most differences with the reference.
What helps
- A Compiler report, whether or not it worked.
- If it works, a pull request that turns the template into a verified profile, as described in step 5 of the guide.
Micro Focus is one of the two compilers that the roadmap to 1.0 needs verified.
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- Avg merge
- 4h 51m
- Merged PRs (30d)
- 9
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from abstracta/cobalto
-
extension help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
compiler help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 Half a day Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
release
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
All issues in abstracta/cobalto
Similar issues
-
hive size:simple
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
A new VOLTTRON_HOME starts with agent isolation mode on (string comparison of a boolean default)Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
painted-porch/marcus#977 ·
Maintainers usually reply within 1 day
-
llm translation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FAIRmat-NFDI/sand#239 ·
Maintainers usually reply within 1 day