Re: Re: [PEPr] Comment on RFC::Requiring E_STRICT Compatibility for NewPEAR Packages
| From: | Pierre | Date: | Mon, 10 Jul 2006 21:57:20 +0000 |
| Subject: | Re: Re: [PEPr] Comment on RFC::Requiring E_STRICT Compatibility for NewPEAR Packages | ||
| References: | 1 2 3 4 5 6 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-43356@lists.php.net to get a copy of this message | ||
On 7/10/06, Lukas Smith <lsmith@php.net> wrote:
Markus Tacker wrote: On a side note: I think this proposal could be extended or accomplished by another proposal to force the prefixing of all new or updated packages with "PEAR_" thus preventing a future collision with PHP classes. I agree. Care to write it up?What's about only P_ I rather prefer prefix all by P_ or something shorter than PEAR (some pacakge names are aleaday way too long...) :) --Pierre