A related question: in a multiple-module ZF app, is your main module named "default" while all of the other modules have names specific to what they are for, or do you rename the default module to something else?
In this case, I usually keep it named "default" just for simplicity's sake, but I've been tempted to rename it to something more meaningful every time I start a new project. -- Hector On Fri, Mar 26, 2010 at 10:29 AM, Matthew Weier O'Phinney <[email protected]>wrote: > -- Bill Karwin <[email protected]> wrote > (on Friday, 26 March 2010, 09:54 AM -0700): > > On Mar 26, 2010, at 9:43 AM, Hector Virgen wrote: > > > I usually have two namespaces, a project-specific one named after > > > the project and a global library that is shared between projects > > > named after the company I am working for. I never use "App" or > > > "My" like most examples. > > > > Indeed, yes! Using generic names for namespaces defeats the > > original purpose of using namespaces -- i.e. trying to prevent your > > class names from conflicting with third-party class names you use in > > the same application. > > > > What if someone were to develop a PHP framework called "My" with a > > class "My\FactoryFactoryFactory"? :-) > > I've always thought of "My" as an "example" namespace (dates back to my > days in Perl, where you'd see "My" as the example package declaration). > > "Application" is what we specify as the default for resources under the > "application" tree -- but even this is fully configurable, and I'd > recommend using one that's project specific. > > -- > Matthew Weier O'Phinney > Project Lead | [email protected] > Zend Framework | http://framework.zend.com/ > PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc >
