Viktor,
Okay, that's also part of the issue. But f.e.
libcurl.dll also uses C RTL, so it depends on MSVCRT.DLL.
[ BTW, all MinGW binaries depend on MSVCRT.DLL ]
AFAIK MSVCRT.DLL is a system CRTL. Normally it is
not used by MSVC, until you explicitly build your
exe against it. MSVC uses its own CRTL (although I
may be wrong here).
Did you use libcurl with Borland harbour.dll compiled
to use Borland dynamic CRTL ? I wonder if it really
works.
Standard ANSI C calls shouldn't be a problem, as they
should work regardless of the underlying C RTL
implementation. Then, I guess the problem may be with
compiler specific C RTL functions (?).
There was a direction way back in time, so that we
should try to use ANSI C functions or direct OS API
calls, while avoiding any C RTL specific functions.
Maybe following the above could clear up such issues,
if we really have them.
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.
Who forces what? I was raising a potential issue/question
and we're discussing it, hopefully everybody will learn
something, but surely nobody loses anything.
I don't see any issue except the one which
will come if we follow your proposition. It
does not solve anything and will block some
possible scenarious.
Or do you want to have a "final word" again ?
Is this REALLY necessary?
Or is Harbour developers' list such a place where
questions cannot be asked about Harbour's properties,
inner workings, design considerations behind certain
moves in the past or current state, or raise any
possible issues without being faced with this comment
again and again?
Final word, yeah: Regardless of any moves made out
this discussion I think it's very important to discuss
why Harbour has harbour-b32.dll and harbour-vc.dll, when
and why should one use any one of them. These questions
are nowhere documented, and very much unclear for me
(and probably for other users downloading binaries, too),
so they would raise anyway as soon as someone would try
to use any harbour.dll at all.
The problem with "final word" is that you do not
want to listen to any resonable arguments. Even
those based on technical details.
--
Marek
----------------------------------------------------------------------
Rowerem po Roztoczu.
Zobacz relacje >>> http://link.interia.pl/f1e65
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
