Mindaugas, Viktor, all
They are not compatible due to different internal naming and
calling convention.
Final user may have many different Harbour applications compiled
by MSVC and BCC using harbour.dll and different names allows to
install both DLLs in system directory.
I understand that, but isn't it the point of .dlls that they
provide a _common_ interface for all programs regardless of the
compiler/tools/C/C++ mode used to generate the .dll and the
user applications using it?
I have a similar opinion. Dll files are used to do function calls from
external application, and these is no restrictions on compiler to be
used to compile this external app.
Sorry guys, but it seems to me you both mix Harbour.dll
with general purpose dll libraries used by a system.
It's not the case. The problem is C standard Runtime
library. Each C compiler has its own dynamic CRTL designed
and compiled for that compiler. Harbour uses C Runtime
library extensivly. If I would like to create and use
Harbour dll which uses *dynamic C Runtime library" I will
not be able to do so - following your aproach.
And in fact I do this. My HbWxW uses Harbour dll AND
dynamic CRTL (Borland build).
So please don't force anything based on your (not real
life) experience with dlls. Current aproach is a good
balance between "dll hell" and a "real life" requirements.
Or do you want to have a "final word" again ?
--
Marek
----------------------------------------------------------------------
W kosciele tez zdarzaja sie wpadki!
Smieszny filmik >>> http://link.interia.pl/f1e61
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
