Re: [Coding Standards] Prefix all classes
| From: | Joshua Eichorn | Date: | Mon, 09 Jul 2007 21:27:40 +0000 |
| Subject: | Re: [Coding Standards] Prefix all classes | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-47309@lists.php.net to get a copy of this message | ||
Paul M Jones wrote:
-joshBut it does make sense that you should be able to install code like: pyrus install pear2/Group_Package or pyrus install PEAR2_Group_PackageOr even ...pyrus install pear2/PEAR2_Group_PackageI don't think PEAR2 is a special case. Anything we do for ourselves, we should expect to see emulated in other channels. Because channel aggregators exist, we should attempt to pre-emptively deconflict with package names from other channels. In fact, I might even go so far as to say that the installer should assume that the first element of the package name is the channel nickname. That would allow for a nice little shortcut, but of course I can't say how easy or hard that would be to implement. I guess my point is that pear2/PEAR2_Group_Package is redundant, its double prefixing which seems a bit pointless