Re: Re: Phpdocumentor memory usage

# neuhauser@bellavista.cz / 2003-03-21 08:30:20 +0100: > # greg@chiaraquartet.net / 2003-03-20 19:37:00 -0500: > > The only thing I want to ensure is that phpDocumentor doesn't depend on > > external entities to work, as much as possible, so that it is a > > run-out-of-the-box tool. As PEAR matures, I want to make it an option > > to depend on the PEAR classes that are used, like HTML_TreeMenu, but not > > a requirement. Same with any non-standard C extensions. So, if > > phpDocumentor uses DB_DataObjects, for example, I'll include the source > > for DB_DataObjects bundled as an option, separate from PEAR, but also > > have a release available that depends on PEAR being installed. Does > > this strike everyone as reasonable? > > Not really. If the library is used without changes, it shouldn't be > bundled. And if it's modified it should be subclassed and then there's no need to bundle the parent either. -- If you cc me or remove the list(s) completely I'll most likely ignore your message. see http://www.eyrie.org./~eagle/faqs/questions.html