Re: [PEPr] +1 for PHP::PHP_Modules

Well... from what I've learned about what modules are, it's not what you perceive them as. Modules are simply code that is loaded and run with the main program and other modules. Also, if you look inside the class, not only does it load code from a file, it also allows the user to execute and reload that code. There will also be variable support built in to it as well. So, by design, this is not just a file/code loader. I would like to ask if anyone else has any issues with the name? PHP_Modules isn't a great name, but it may be the best name. I don't see a need to change it from one "high level and abstract" name to another that doesn't truly describe what the class does. Thanks, ~ Eric Gach Alan Knowles wrote:

just doing a google search for module gives you an idea of the problem Modules - are Perl equivilant to PHP packages. (does it load these) 'Collection of PECL Modules' from php.net/downloads (does it load these?) Modules are components of phpnuke/postnuke/xoops etc. (does it load these?) What does your package do? - it extracts and Loads (or includes) specific PHP Code from a PHP File. At a higher level, your package may allow you to write modular applications.. - but then again so does PHP.. The names you mention, are still very 'high level and abstract' - It may mean something to you, but it doesnt instantly explain what the package does, and how it would be of any use to anyone else. Regards Alan Eric Gach wrote:

Alan Knowles wrote:

The Problem is, that Modules a extremely abstract word.. - modules of what? and what does it do with these modules?

I thought that was kind of explanatory by the PHP in the name. They're PHP Modules to make the script more modular.

If it intends to support Classes and Functions then PHP_CodeLoader

I don't see how that is any clearer than PHP_Modules... but I've put some thought into it and got some suggestions. As far as new names for the class, what about PHP_ModularCore or PHP_ModularFramework? Both are equally centered around the idea that it enables modular support in PHP scripts.

Is probably far more descriptive and suitable..? Regards Alan Eric Gach wrote:

Alan, PEPr wrote:

Alan Knowles (http://pear.php.net/user/alan_k) has voted +1 on the proposal for PHP::PHP_Modules. Proposal information: http://pear.php.net/pepr/pepr-proposal-show.php?id=68 Vote information: http://pear.php.net/pepr/pepr-vote-show.php?id=68&handle=alan_k This vote is conditional. The condition is: Please choose a more descriptive name.

This name, I feel, is suitable for the project because of plans I have for future development. These plans include extending support for not only just modules/functions but for classes. Variable support will also be something worked into this, as well as other module dependencies. So as far as another name goes... I believe this one is descriptive enough due to the fact that it loads modules and not just functions.

Thanks, ~ Eric Gach