Re: Re: [PEPr] -1 for RFC::Prefix all classes with PEAR_
| From: | Joshua Eichorn | Date: | Fri, 06 Oct 2006 20:45:40 +0000 |
| Subject: | Re: Re: [PEPr] -1 for RFC::Prefix all classes with PEAR_ | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-44427@lists.php.net to get a copy of this message | ||
Lukas Kahwe Smith wrote:
Philippe Jausions wrote:We only get to add a global prefix once. In a sense its a get out of jail free card in terms of backwards compatability and making major changes, we should use it wisely. -joshI also think that applying this to top level categories is senseless. It does not solve the original issue of namespace clashes. Just because it may be less likely, does not mean that it will be any less painful when it does happen. regards, Lukas We should use this opportunity to move packages to better categories not just do an unclear RFC about a new prefix.I agree to the voices that say this proposal should only be applied to top level classes.I think only doing partial prefixing on top classes will leading to inconsistencies within PEAR packages... some with prefix and some without.