[PEPr] Comment on RFC::Prefix all packages with P_
| From: | Philippe Jausions | Date: | Wed, 12 Jul 2006 00:44:28 +0000 |
| Subject: | [PEPr] Comment on RFC::Prefix all packages with P_ | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-43387@lists.php.net to get a copy of this message | ||
Philippe Jausions (http://pear.php.net/user/jausions) has commented on the proposal for RFC::Prefix
all packages with P_.
Comment:
Prefixing classes with something clearly marking the class as part of the
PEAR framework is definitively needed.
Besides that, "P_" is the most unsexy thing to use. Yes it's short, but
frankly that would actually hurt PEAR, from a marketing prospective, and
would probably also conflict with users applications. We should either use
Pear_ (to make the distinction with the PEAR package and sub-class) or
think about something completely different and doing so allow a rebranding
of PEAR. BTW, prefixing class names would allow to go to Pear_MDB instead
of Pear_MDB3, which is why maybe a rebranding could help...
Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=420
--
Sent by PEPr, the automatic proposal system at http://pear.php.net