I don't remember exactly which update had this change. mod where the source had DLLIMPORT instead of DLLEXPORT. Before that change (which my memory says I lobbied for), you had to supply a separately compiled. But it wasn't always this way, and the version he has doesn't have that behavior. In CVF 6.6C (and the later Intel compilers), when you USE a module that has a DLLEXPORT directive, that turns into a DLLIMPORT, hence my advice above. I was able to log in to Bakhbergen's PC and eventually figured out the problem. Otherwise A, B and S are local variables. To the module, so that the main program can see the module variables from the DLL. Any advice would be greatly appreciated.īTW, the same algorithm without using the DLL works well and gives correct result: PROGRAM AMAIN3 The second case (with the use of module) represents the structure of my large source-code so I need to resolve this issue. I have built DLL and LIB files from the visual development environment. zero): PROGRAM AMAIN2Īs can be seen above, DLL contains only subprogram in both cases (SUBRO1 and SUBRO2, respectively).
However, if I implement the same algorithm using the module, I get inconsistent result (i.e. The following code works just fine: PROGRAM AMAIN1 FALSE.I need to create and use dynamic-link library (DLL) for Fortran application using Compaq Visual Fortran 6.6. IMPLICIT NONE CONTAINS !- ELEMENTAL LOGICAL FUNCTION lt(a, b) INTERFACE ELEMENTAL LOGICAL FUNCTION f(x1, x2) IMPLICIT NONE CONTAINS !- RECURSIVE FUNCTION qsort2(x, f) RESULT(res)
0 kommentar(er)
