On Sunday 15 January 2006 10:59, rubicant rubicant wrote:
> I'm trying to suggest that GCC should have error codes to describe
> errors, continue reading on if you like the idea or not ;-)
>
> THE IDEA:
> The idea is to make GCC better when it comes to error reporting. This
> will be done using so
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
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
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,
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 t
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
