Skip to main content

DLL Convention

  • Oct 10, 2017 9:58 AM UTC
  • 2 replies
  • 6 views

Dominique Sacre
Forum|alt.badge.img+2

Hi all.

We notice that from runtime versione 9.2.2 (or higher) the DLL convention seemes to be automatic set by the runtime ignoring the user specification.

Is it correct ? Can we trust it and stop explicitly setting the environmental variable ?

 

Thank you

--

Davide Giudici


#extend
#DLL
#AcuCobol

2 replies

Stephen Hjerpe
  • Participating Frequently
  • Oct 11, 2017 5:19 PM UTC

Hi all.

We notice that from runtime versione 9.2.2 (or higher) the DLL convention seemes to be automatic set by the runtime ignoring the user specification.

Is it correct ? Can we trust it and stop explicitly setting the environmental variable ?

 

Thank you

--

Davide Giudici


#extend
#DLL
#AcuCobol

The default value for DLL_CONVENTION is 0 - which is the standard C convention. Are you saying that setting DLL_CONVENTION=1 (Pascal convention) gets overwritten in some manner? If so, please contact Customer Care with your example of this behavior.


Dominique Sacre
Forum|alt.badge.img+2

Hi all.

We notice that from runtime versione 9.2.2 (or higher) the DLL convention seemes to be automatic set by the runtime ignoring the user specification.

Is it correct ? Can we trust it and stop explicitly setting the environmental variable ?

 

Thank you

--

Davide Giudici


#extend
#DLL
#AcuCobol
No, I mean that seems to be impossible to set the wrong dll convention on "new" version of the runtime. This is good, but I wish to have a sort of "official" check.