[PEPr] Comment on RFC::Package naming, file naming and directory structure RFC
| From: | PEPr | Date: | Mon, 19 Apr 2004 17:26:04 +0000 |
| Subject: | [PEPr] Comment on RFC::Package naming, file naming and directory structure RFC | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-28069@lists.php.net to get a copy of this message | ||
Justin Patrin (http://pear.php.net/user/justinpatrin) has commented on the proposal for RFC::Package
naming, file naming and directory structure RFC.
Comment:
I definately like the idea of enforcing package names to be classified by their categories and
keeping class names the same as the path to the class (as this helps quite a bit with includes,
factories, and such).
However, I think a provision for sub-packages needs to be added. For instance,
DB_DataObject_Formbuilder is a package for DataObject and (IMHO) should stay where it is in a
DataObject directory. Naming if DB_DataObjectFormbuilder breaks the path / naming convention unless
you put it in a DataObjectFormbuilder.php file which seems unneccesary and confusing.
So I would propose adding a provision for packages which are made to work as an extension or an
addition to another class be allowed to treat the package they extend as their Category Prefix,
Multiple underscores would also have to be allowed for this.
Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=55
--
Sent by PEPr, the automatic proposal system at http://pear.php.net