Frank Schönheit - Sun Microsystems Germany wrote:
Sure, there are other means to hide implementation. All have advantages
and disadvantages (e.g. if somebody prefers inheritance over
composition, then factories for interfaces are not the way to go). I
IMPL pointers are not the way to go as well, if you want inheritance ...
consider PIMPL one valid solution for certain situations (e.g. extending
I trust you here ... :-)
a complex class hierarchy - with millions of lines of code, grown in
decades - without completely rewriting it :).
That seems to be one of your favorite arguments ... :-)
They already have an OOo build env with complete dependencies, so what
stops them from joining? SCNR :)
Ok, this is not hurdle, you are right.
However, in my opinion, the increased average efficiency in the daily
work is worth this trouble from time to time ...
Mmmm, several times I had to fix "bugs" which just were build problems,
because of not understood dependencies.
Sure, me too. I don't say there are no drawbacks, I'm just saying they
might be smaller than if we had complete dependencies (in the current
build env).
So, lets look forward to Kais improvement ...
Ciao
Frank
Kay
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
