Re: [Coding Standards] Prefix all classes

David Coallier wrote:

On 7/9/07, Paul M Jones <pmjones@ciaweb.net> wrote:

Hi all -- I'm going to offer discussion points on the coding standards proposal under separate subject lines, all prefixed with [Coding Standards]. This should make the separate discussions easily addressable. The section titled "Prefix all classes" states:

PEAR2_ prefix is required of all class names, package names, however, will not have a PEAR2_ prefix because in most cases, the installation will be like: pear install pear2/PackageName

I think the PEAR2_ prefix should be on the package name as well. Although it adds typing, it also adds consistency. As an incidental benefit, this will aid name de-confliction for channel and package aggregator services like Pearified, Pearadise, etc.

Yes.. a keyboard is meant to type.. PEAR2_ is not taking 3-4 hours to type. I'm all for using PEAR2 everywhere.. Having every package named PEAR2_Group_Packagename makes for a really ugly listings on the command line and in the user interface.

But it does make sense that you should be able to install code like: pyrus install pear2/Group_Package or pyrus install PEAR2_Group_Package -josh