[PEPr] Comment on RFC::Package naming, file naming and directory structure RFC

Alexey Borzov (http://pear.php.net/user/avb) has commented on the proposal for RFC::Package naming, file naming and directory structure RFC. Comment: I am against this RFC. It looks very poorly thought out and does not solve any immediate problems, only adds unnecessary micromanagement. *Package naming* Packages having the names of the category (e.g. DB), packages in top-level namespace (e.g. LiveUser), subpackages (e.g. HTML_QuickForm_Controller), packages within two-level categories (HTML_Template_Whatever) are not covered by this. Enforcing this rule can lead to an extreme BC breaks due to package renaming. *Class naming* This will lead to BC breaks due to class renaming and will create extremely verbose class names. E.g. HTML_QuickForm_Action_Display will become HTML_QuickForm_Controller_Action_Display. *File naming* "One class per file" rule in not explained. It will lead to unnecessary performance degradation as loading a file is a slow operation in PHP. *Directory structure* With current installer infrastructure it is impossible to enforce such directory structure without extreme Black Magick: http://marc.theaimsgroup.com/?l=pear-dev&m=108194838321902&w=2 I'll agree with this section only after a cleaner way to do this is in place. 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