Re: [PEPr] Proposal finished PHP::PHP_Modules

On May 21, 2004, at 8:33 AM, Greg Beaver wrote:

Eric Gach wrote:

PEPr wrote:

PEPr has automatically finished the proposal on PHP::PHP_Modules. Further details on the status of the proposal and the votes can be found here: http://pear.php.net/pepr/pepr-proposal-show.php?id=68

Okay... so since we haven't got much said about the name, I'd like to discuss a few other ideas. I'm still not wanting to rename this class to PHP_CodeLoader as previously suggested because it just doesn't give the

Since there has only been negative feedback, I'd like to point out that I think PHP_Modules is the clearest package name of those suggested. The only thing missing from the name is "reloadable" but adding this would make it ridiculously long. People looking for a custom reloadable component will first search for module. Why? The most popular PHP-based CMS systems, phpnuke/postnuke/xaraya/xoops use the term "module" to describe reloadable components. Module is not a core PHP term - there is no such thing. In my opinion, any other name would simply be confusing. The only addition to the name that might make it even clearer would be something like PHP_DynamicModule, but on the other hand, the name PHP_Module sparks interest that leads one to read the manual, and the first paragraph will describe the dynamic nature of the package, since that is the whole point.

Agreed with Greg here; "Module" is clear, succinct, and in common use among its target audience. -- Paul M. Jones Savant: the simple alternative to Smarty for PHP. http://phpsavant.com/ DB_Table: build RDBMS tables and XHTML forms in one PHP class. http://wiki.ciaweb.net/yawiki/index.php?area=DB_Table Yawiki: your collaborative online documentation system. http://wiki.ciaweb.net/yawiki/index.php?area=Yawiki Yawp: a single-file foundation for PHP applications. http://phpyawp.com/