My name is Emílio, I'm a developer mainly in Microfocus dialect, now in a development project in Acucobol programs. For reason of licences, my question is:
I can compile my Cobol fonts Acucobol in OpenCobol ? Wich the learn curve ?
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You should be able to compile your acu programs with cobc -std=acu-strict prog.cob, please report if you get compiler errors.
You should try with GC 3.1.2 or 3.2-dev, you'll be out of luck with different versions, especially with the old OpenCOBOL.
In general I've found the GnuCOBOL messages commonly to be much clearer than the ACUCOBOL-GT ones and don't expect a big learning curve.
If you use the huge amount of ACU's SCREEN SECTION extensions, especially the control-types you'll have to either find someone to add those to GnuCOBOL or rewrite those, GC "skips" most of those during compilation with a warning, but won't handle them at runtime.
If the sources in the acu dialect are primarily batch programs you should be quite fine, the only thing (out of the blue) you'd possible need to adjust is checking of COBOL standard io status values instead of (or additional to the ones returned by ACUCOBOL-GT).
You may see some 'C$' programs missing in the stock library, but most of those should be relative easy to add (also possible as "pure COBOL" module).
Support for "W$" routines is unlikely to be seen, but could be added, at least on your local site.
After all: you can get GnuCOBOL 3.1.2/3.2dev at any time and just try the compilation of everything and ask back for specific issues you may see.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good Afternoon, Dears.
My name is Emílio, I'm a developer mainly in Microfocus dialect, now in a development project in Acucobol programs. For reason of licences, my question is:
I can compile my Cobol fonts Acucobol in OpenCobol ? Wich the learn curve ?
Thanks.
You should be able to compile your acu programs with
cobc -std=acu-strict prog.cob, please report if you get compiler errors.You should try with GC 3.1.2 or 3.2-dev, you'll be out of luck with different versions, especially with the old OpenCOBOL.
In general I've found the GnuCOBOL messages commonly to be much clearer than the ACUCOBOL-GT ones and don't expect a big learning curve.
If you use the huge amount of ACU's
SCREEN SECTIONextensions, especially the control-types you'll have to either find someone to add those to GnuCOBOL or rewrite those, GC "skips" most of those during compilation with a warning, but won't handle them at runtime.If the sources in the acu dialect are primarily batch programs you should be quite fine, the only thing (out of the blue) you'd possible need to adjust is checking of COBOL standard io status values instead of (or additional to the ones returned by ACUCOBOL-GT).
You may see some 'C$' programs missing in the stock library, but most of those should be relative easy to add (also possible as "pure COBOL" module).
Support for "W$" routines is unlikely to be seen, but could be added, at least on your local site.
After all: you can get GnuCOBOL 3.1.2/3.2dev at any time and just try the compilation of everything and ask back for specific issues you may see.