Prev: Socket performance
Next: 'as' keyword - when/how to use it
From: Carl Banks on 24 Jul 2010 15:23
On Jul 23, 7:42 pm, Rolando Espinoza La Fuente <dark...(a)gmail.com>
wrote:
> TL;DR: if you want to stay sane, don't inherit two classes that share
> same inheritance graph
[snip rest]


If you want to stay sane, don't inherit from ANY class unless

A. you own it, or
B. it's explicitly documented as supporting inheritance

Furthermore, if you want to stay sane, don't mulitply inherit from any
class unless

A. you own it, or
B. it's explicitly documented as supporting MULTIPLE inheritance


Inheritance is always risky if you don't know what you're inheriting
from.


Carl Banks
First  |  Prev  | 
Pages: 1 2
Prev: Socket performance
Next: 'as' keyword - when/how to use it