Re: [PEPr] -1 for RFC::Prefix all classes with PEAR_

We will not upgrade existing packages, this rule would apply to new packages. This would be terrible for BC. Waiting for namespaces is a bad strategy. New packages have to be PHP5 anyway so this proposal does make sense as it applies to new packages or maintainers who want to prefix, in which case this would need to be a new Package2. What do you have in mind for Pear and PHP5. A PEAR2 installer that works only in PHP5 ? (don't mean to sound dry, it's just a question :) Arnaud. Joe Stump wrote: > Joe Stump (http://pear.php.net/user/jstump) has voted -1 on the proposal for RFC::Prefix all > classes with PEAR_. > > Proposal information: > http://pear.php.net/pepr/pepr-proposal-show.php?id=420 > Vote information: > > http://pear.php.net/pepr/pepr-vote-show.php?id=420&handle=jstump > > Comment: > > I concur with Ian. With the current state of the PEAR Group and a > non-existant QA department who's going to manage adding PEAR to all of the > packages? > > We should let PEAR for PHP4 die a slow death and worry about this sort of > stuff with regards to a PEAR for PHP5. That or wait for namespaces. > > I, as well, don't plan on putting PEAR in front of any of my packages (at > least until PHP releases a 'Net_Curl' class or a 'Payment_Process' class). >