I'd call it the most convenient, since you don't need implibs at all,
of course you can't link any .dlls with non-matching calling
convention,
but it this case no implib would help anyway.
Here is the problem.
I use Eztwain.dll from www.dosadi.com. I wrote all the wrappers which
work fine with MSVC and BCC but I have not been able to get it working
with MINGW ( probably a show stopper in my case ), it does not matter
how hard I try with different approaches.
In such case some tricks are inevitably needed. If eztwain was
written in C++, chances aren't very high you can make it work,
but the best place to ask for advice is the product developers,
this seems to be a commercial product, so maybe they are available
for help.
A TWAIN interface contrib would be BTW very nice in Harbour.
b is buggy, so it will something give strange
results. (openssl, libcurl)
I do not know, nor did I say the "implib" is buggy. Just explained
that
*I* did say that it's buggy :) Maybe my sentence sounded ambiguous.
The point is that it doesn't work reliably, and it will fail
in random places (when your least expect it of course).
In case of BCC, users should also know that BCC uses an incompatible
name mangling when creating .dlls, so if interoperability for .dll
targets is a concern, BCC should be dropped.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
