Re: Fwd: GnuCOBOL call parameter problem.

[Ron Norman]

I will test this using Microfocus and see what happens.

I regularly use C -- calling COBOL -- calling C but never looping back to calling COBOL again.

Just getting the C API working a few years ago was a far bit of effort but I will have another look.

Being compatible with Microfocus is an important feature of GnuCOBOL.

On Fri, Jun 5, 2020 at 4:30 PM James K. Lowden <jklowden@schemamania.org> wrote:

On Thu, 4 Jun 2020 14:35:21 -0400
Ron Norman <rjn@inglenet.com> wrote:

> GnuCOBOL supports many of the same routines defined by Microfocus...
...
>     cobcall ("routine1",2,argv);

Hmm.  Section 11.8.5. of the cobc Programmer?s Guide, "C Main Programs
Calling GnuCOBOL Subprograms" does not mention cobcall.  The string
"cobcall" does not appear in that manual, nor in the info file.  This,
as John Cleese might say, is an ex-function. 

Nor is cobcall a good idea.  A good idea is what the Programmer's Guide
documents: Cobol functions called from C programs with the C calling
convention, full stop.  Maybe the library has to be initialized, sure,
fine, OK.  But a special gateway function to call all other functions?
Why? 

If we want to include -- and document -- cobcall for compatibility
purposes with MF, that's also fine.  But we shouldn't require it or
depend on it. 

Can you explain how deep the current dependency goes, and what in your
mind would be needed to get rid of it? 

--jkl

--

Cheers

Ron Norman