Re: [PEPr] Comment on RFC::Prefix all packages with P_

Hi, On 7/12/06, Justin Patrin <papercrane@gmail.com> wrote:

Again, this RFC proposes a solution to a problem that doesn't exist. If the problem doesn't exist, why are we trying to fix it? We end up fixing something that doesn't need fixing and at the same time creating several _real_ problems. I must say that I entirely agree with Scott here. If we had done this a few years ago maybe it would be ok, but seeing as PHP6 is supposed to have namepsaces I don't think that putting this RFC in place is going to solve anything. Not to mention that this will cause massive upgrade pains for all packages. PEAR has been fine until now. I think it will be fine for a while yet.

Is it me or you (both) still don't realize that this change will happen only for major release or new packages? And major version updates give always more work anyway. I'm really not sure that php6 will have namespace support, I would say the chance is about 60% now. It will also not be available anytime soon (within a year) and will not be widely adopted in 2-3 years. I can be wrong here, but the last major php releases worked like that. So are we going to ask again the php developers to do not add classes, functions or constants using reserved words or common names? and for the next 3-4 years? The answer is clear: no. Not because we cannot ask, but because they will tell us to go to hell (to be honest, they already did). Cheers, --Pierre