11.11.2015 18:03, Jim Starkey wrote:
> Implementing an interface doesn't require
> multiple inheritance -- or any inheritance, for that matter -- just a
> decently designed language.
Yes. But in this case the design requires implementing of two different
interfaces at
once. And inheritance
On 11/11/2015 11:29 AM, Dimitry Sibiryakov wrote:
> 11.11.2015 16:22, Jim Starkey wrote:
>> Multiple inheritance with common base classes is, in fact, a mess. The
>> problem is that the C++ compiler can't really know whether two like
>> named methods in different classes are the same and has no way
11.11.2015 16:22, Jim Starkey wrote:
> Multiple inheritance with common base classes is, in fact, a mess. The
> problem is that the C++ compiler can't really know whether two like
> named methods in different classes are the same and has no way to known
> which to reference in vtable. This shows u
On 11/11/2015 6:52 AM, Adriano dos Santos Fernandes wrote:
> On 11/11/2015 09:37, Dimitry Sibiryakov wrote:
>> 11.11.2015 12:32, Adriano dos Santos Fernandes wrote:
>>> I can write almost any code mixing their common part in a single class,
>>> avoiding duplicate declarations, with our without cloo
11.11.2015 13:55, Adriano dos Santos Fernandes wrote:
> Well, I initially would not gonna to reply to your messages, as I saw
> you were just lazy, just replied because you directed it to me, but you
> were just lazy and wanna I do your job.
Documenting of your design is my job? Wow...
--
On 11/11/2015 10:49, Dimitry Sibiryakov wrote:
> 11.11.2015 13:44, Adriano dos Santos Fernandes wrote:
>> I guess it will not, as even without the magics behind in the code, it
>> would not gonna work directly.
>You guess? You don't know how your code work?..
>
Well, I initially would not gonn
11.11.2015 13:44, Adriano dos Santos Fernandes wrote:
> I guess it will not, as even without the magics behind in the code, it
> would not gonna work directly.
You guess? You don't know how your code work?..
--
WBR, SD.
-
On 11/11/2015 09:57, Dimitry Sibiryakov wrote:
>Right now, in current state of source tree, will work a class derived from
> IKeyHolderPluginImpl and ICryptKeyCallbackImpl? Yes or no?
>
Sorry, but this is something you can verify yourself.
I guess it will not, as even without the magics behin
11.11.2015 12:52, Adriano dos Santos Fernandes wrote:
> Definitively, not always out of the box when they have common base classes.
Even in this case it works predictable in standard C++.
>> >So, what is your answer: is using of multiple inheritance possible with
>> > CLOOP templates
>> >
On 11/11/2015 09:37, Dimitry Sibiryakov wrote:
> 11.11.2015 12:32, Adriano dos Santos Fernandes wrote:
>> I can write almost any code mixing their common part in a single class,
>> avoiding duplicate declarations, with our without cloop, and as the one
>> you say, it will not work too, but will be
11.11.2015 12:32, Adriano dos Santos Fernandes wrote:
> I can write almost any code mixing their common part in a single class,
> avoiding duplicate declarations, with our without cloop, and as the one
> you say, it will not work too, but will be much more compact!
Multiple inheritance of norma
On 11/11/2015 09:18, Dimitry Sibiryakov wrote:
> 11.11.2015 12:10, Adriano dos Santos Fernandes wrote:
>> Why it can be made more simple and readable this way?
>No need to use delegation. No second object declaration, initialization
> and
> cross-references with "parent" member. The code is t
11.11.2015 12:10, Adriano dos Santos Fernandes wrote:
> Why it can be made more simple and readable this way?
No need to use delegation. No second object declaration, initialization and
cross-references with "parent" member. The code is two times shorter.
--
WBR, SD.
On 11/11/2015 09:01, Dimitry Sibiryakov wrote:
>Hello, Adriano.
>
>Key holder example can be made more simple and readable by using multiple
> inheritance.
> With normal classes I would do it this way:
>
> class CryptKeyHolder: public IKeyHolderPlugin, public ICryptKeyCallback
>
>Is i
14 matches
Mail list logo
