Re: Re: Phpdocumentor memory usage

please limit the quoted material to necessary context. # 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. 1.2.0b3 contains at least HTML_TreeMenu and Smarty, and I don't see any benefit in doing this as opposed to using the ones installed on the system (which might require the user to install them). This, of course, matters only for libraries that have been publically released. Bundling a class from PEAR that is only available from CVS ATM is another thing. -- 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