On Oct 10, 2005, at 2:25 PM, Frans Englich wrote:
What makes me ask these questions, is that I have code which
(according to my
opinion) severely needs virtual inheritance(VI). The code VI would
affect is
not under my veto power, and the maintainers of that code have so
far given
as comment "
On Monday 10 October 2005 15:21, Frans Englich wrote:
> Hello all,
>
> In a large project I'm participating in, a design dilemma have arrived.
> Adding virtual inheritance would solve it beautifully on the source code
> level, but a potential drawback is the speed penalty it brings. Measurement
> i
Frans Englich wrote:
> On Monday 10 October 2005 22:29, Mark Mitchell wrote:
>
>>Frans Englich wrote:
>>
>>>Followup question: what is the increased cost of calling a non-virtual,
>>>inlined function('inline' keyword) on a virtual base?
>>
>>None, if the function is inlined -- and whether it is in
On Monday 10 October 2005 22:29, Mark Mitchell wrote:
> Frans Englich wrote:
> > Followup question: what is the increased cost of calling a non-virtual,
> > inlined function('inline' keyword) on a virtual base?
>
> None, if the function is inlined -- and whether it is inlined or not
> should not be
Frans Englich wrote:
> Followup question: what is the increased cost of calling a non-virtual,
> inlined function('inline' keyword) on a virtual base?
None, if the function is inlined -- and whether it is inlined or not
should not be affected by whether or not it is in a virtual base.
> What m
On Mon, Oct 10, 2005 at 09:25:15PM +, Frans Englich wrote:
> Followup question: what is the increased cost of calling a non-virtual,
> inlined function('inline' keyword) on a virtual base?
If the function is successfully inlined, then the question really refers
to the cost of the code inside
On Monday 10 October 2005 18:53, Mark Mitchell wrote:
> Frans Englich wrote:
> > Hello all,
> >
> > In a large project I'm participating in, a design dilemma have arrived.
> > Adding virtual inheritance would solve it beautifully on the source code
> > level, but a potential drawback is the speed p
Frans Englich wrote:
> Hello all,
>
> In a large project I'm participating in, a design dilemma have arrived.
> Adding
> virtual inheritance would solve it beautifully on the source code level, but
> a potential drawback is the speed penalty it brings. Measurement is always
> the way of approa
On Monday 10 October 2005 16:12, Jonathan Wakely wrote:
> Frans Englich wrote:
> > In a large project I'm participating in, a design dilemma have arrived.
> > Adding virtual inheritance would solve it beautifully on the source code
> > level, but a potential drawback is the speed penalty it brings.
Frans Englich wrote:
> In a large project I'm participating in, a design dilemma have arrived.
> Adding
> virtual inheritance would solve it beautifully on the source code level, but
> a potential drawback is the speed penalty it brings. Measurement is always
> the way of approaching performan
Hello all,
In a large project I'm participating in, a design dilemma have arrived. Adding
virtual inheritance would solve it beautifully on the source code level, but
a potential drawback is the speed penalty it brings. Measurement is always
the way of approaching performance questions, but si
11 matches
Mail list logo
