Re: [PEPr] -1 for RFC::Prefix all classes with PEAR_
| From: | Lukas Kahwe Smith | Date: | Wed, 04 Oct 2006 19:05:32 +0000 |
| Subject: | Re: [PEPr] -1 for RFC::Prefix all classes with PEAR_ | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-44325@lists.php.net to get a copy of this message | ||
Joshua Eichorn wrote:
Arnaud Limbourg wrote:*sigh* the proposal seemed all clear to me .. but i guess the way things are turning it needs to be clarified further. the purpose of this RFC was to cover _new_ packages (which includes new major versions). these new versions may be php4 packages until the deadline that was decided in another rfc, but will more likely be php5 only packages. regards, LukasJoshua Eichorn wrote:Its just a poorly written RFC, just like the PHP5 one. If this is only for new packages targeted at php5 it should say so it doesn't. The RFC says: -- snip Purpose of this proposal The class names of all packages should be prefixed with /PEAR_/. -- end snip I see the word All how about you -- snip Affected releases Changing the class name is considered a BC break. Packages must be updated if a BC break is allowed according to the version naming guidelines [3 <http://pear.php.net/group/docs/20040226-vn.php>]. -- end snip This is even lamer, it says i'd have to name my new package PEAR_HTML_AJAX2Joshua Eichorn (http://pear.php.net/user/jeichorn) has voted -1 on the proposal for RFC::Prefix all classes with PEAR_.This is the type of change that should be targeted at new php 5.2 versions of classes not at existing code.It is only for new packages and new packages must be PHP5 (i can't find an RFC on this though I remember a discussion where everybody agreed that new packages should be PHP5). Arnaud.