Re: [Ekiga-devel-list] Design of the engine : why abstract Ekiga::Foo and Ekiga::FooImpl matter

2015-01-14 Thread Julien Puydt
Hi, Le 14/01/2015 10:32, Eugen Dedu a écrit : On 14/01/15 08:43, Julien Puydt wrote: I think the purely abstract Ekiga::Foo and Ekiga::FooImpl is better : it is more expensive, but you do get what you paid for. Hi Julien, In case my opinion is useful: I think you are right in theory and als

Re: [Ekiga-devel-list] Design of the engine : why abstract Ekiga::Foo and Ekiga::FooImpl matter

2015-01-14 Thread Eugen Dedu
On 14/01/15 08:43, Julien Puydt wrote: Hi, this mail is meant to explain why having two classes doesn't make the code more complex just for the sake of it, but because it brings nice features. The fact that Ekiga::Foo is purely abstract means : 1. that anyone trying to write an instance of i