Viktor,
I don't use harbour.dll at all (never exactly understood
its details and benefits), but since I've built all
binaries for Windows, I was wondering why are we having
to differently named ones, a practice which I haven't
seen in any other projects before.
So read my answer to Mindaugas, where I quoted MSVC docs
about the issue I was trying to show to both of you.
Answering to your question, I'm not sure if I'd want to
use Borland dynamic C RTL. Why is it better than using
the static one?
It's not a matter of "being better or worse". It's a matter
of "working" at all. Some projects WILL NOT work without dynamic
CRTL. That's a matter of fact. You have to deal with it.
And back to the first one, what is the
benefit of harbour-*.dll? (no pun intented, I'm really
interested, and I don't want to remove it either.)
Some libraries have to be compiled to dll. Otherwise
they will not work at all. That's their nature. An
example is HbWxW. There are literaly hundreds of classes
in it, each of them being in a separate obj. Those
classes create other classes dynamicly during runtime.
So often there is no reference to some class from your
code, but it has to be created. Because it is not
referenced by your code you would have to REQUEST it
explicitly. But you do not know WHICH one will be
created in general - it's internal part of a librbary.
So you would have to REQUEST ALL classes from library,
causing the final exe to be simlpy HUGE - each exe created
would contain ALL classes. Having a library in dll
solves the problem in an elegant way.
[ The issue so far:
1) C calling convention differences (solvable)
2) name mangling differences (solvable)
3) C RTL interaction and dependency
Multiple issues, the exact specifics are not exactly clear
to me yet. ]
So read my answer to Mindaugas, where I quoted MSVC docs
about the issue I was trying to show to both of you.
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.
I was asking question to have a clearer picture
about this "issue", let's call it topic.
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.
I have no doubt that you know what you're talking
about, but it's really difficult to discuss even a
technical thing when you consider a mere question
an attack. I'd prefer to read more on the technical
details rather.
I DO NOT cosider it an attack. I consider it *FORCING*.
If this is a tabu issue in some sorts of ways, let's move on.
Tabu ? You can call it TABU if you do not want to listen
arguments.
--
Marek
----------------------------------------------------------------------
Najciekawsze miejsca w Polsce i na swiecie!
Zobacz >>> http://link.interia.pl/f1e60
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
