Re: Documention problems

> It's nice for this ascii art :) but not for performance and also > increases the oo overhead. If I don't use any method from the base Mail > class why should I extend from Mail when I can directly extend from > PEAR? Performance issue: Using PEAR means to use a lot of objects ( Errorhandling!). A few more didn't counts. Then, keep the ZendEngine2 in mind, it will improves the speed of object handling. And as the killing argument to your last question: Did you use $var or $HTTP_POST_VARS['var']? I think the last for good reasons, although you now that is slower then the first. We are professional enough to prefer a proper solution instead of looking for every nano seconds of the execution time? OO issue: Take a look into the future. Lets say, you have tons of classes Net. Some of them inherit PEAR from Net_*, some directly, some inherit nothing. And you want to start writing a new class for Net. It's your first time, that you are looking on the source of the other Net classes, you will get confused! No system, no starting point, should i extend PEAR or xyz and why, some does it, some not. > But this is not yet implemented, so IMHO the change should be reverted. > What are the advantages of having a bounch of useless extra methods > avaible? I know, i thought a long time about the change. But this the reason, why i want a package parent class. This would avoid such situation.