Re: Documention problems

Alexander Merz wrote: > > > I refuse to fill my code with crud to get around bugs in PHPDoc. This > > should be fixed in PHPDoc or one of the alternatives. > The @package behavior isn't a bug! It is the same in Javadoc. > > Try to make a sketch about the oo structure of ie Mail_* today > > +PEAR > | > +--+Mail > | | > | +Mail_mail > | +Mail_smtp > | +Mail_sendmail > | > +Mail_mime > > Mail_rfc822 > > Thats confusing, the @package problem is only a part of the careless hierarchy. > I want a proper hierarchy. > > +PEAR > | > +--+Mail > | > +Mail_mail > +Mail_smtp > +Mail_sendmail > +Mail_rfc822 > +Mail_mime > 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? I saw your change in the mime class and though that perhaps it's not a bad idea to have the extra option of sending mails directly from the mime class: $mime->factory('sendmail'); //mime build actions $mime->send(); // auto fills headers and body 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? Tomas V.V.Cox