Thorsten Behrens wrote:
Stephan Bergmann [EMAIL PROTECTED] writes:
That is, from my side: go ahead.
Hi Stephan, all,
well, finally got around doing just that. Issue
http://www.openoffice.org/issues/show_bug.cgi?id=72499
contains a patch, that adds said functionality, and addresses a few
Stephan Bergmann [EMAIL PROTECTED] writes:
I saw your patch yesterday and only had a quick glance at it. What I
do not understand is whether those few ambiguities/incomplete types
across OOo are related to the Reference change (i.e., whether the
Reference change introduces an incompatibility
Thorsten Behrens wrote:
Stephan Bergmann [EMAIL PROTECTED] writes:
I saw your patch yesterday and only had a quick glance at it. What I
do not understand is whether those few ambiguities/incomplete types
across OOo are related to the Reference change (i.e., whether the
Reference change
Thorsten Behrens wrote:
Stephan Bergmann [EMAIL PROTECTED] writes:
I saw your patch yesterday and only had a quick glance at it. What I
do not understand is whether those few ambiguities/incomplete types
across OOo are related to the Reference change (i.e., whether the
Reference change
Thorsten Behrens wrote:
Stephan writes:
I vaguely remember having discussed this before with Daniel Bölzle,
but neither of us can remember whether there were any serious problems
with it.
Well, will of course try this on a full build ;-)
Whether or not the constructor should be explicit
Stephan Bergmann [EMAIL PROTECTED] writes:
Third, the implicit option you proposed where you can implicitly use
xDerived for the up-cast.
That the third most closely mimics plain pointers does not
automatically qualify it as the best solution. Too much implicit
conversion can make code
Thorsten Behrens wrote:
Stephan Bergmann [EMAIL PROTECTED] writes:
Third, the implicit option you proposed where you can implicitly use
xDerived for the up-cast.
That the third most closely mimics plain pointers does not
automatically qualify it as the best solution. Too much implicit
Stephan writes:
I vaguely remember having discussed this before with Daniel Bölzle,
but neither of us can remember whether there were any serious problems
with it.
Well, will of course try this on a full build ;-)
Whether or not the constructor should be explicit might be a
question of
