Talk:PEAR2 Naming Standards

Issues we need to Address:

We need to add examples
- I can do this once issues have been addressed
People don't link a mix of _ and :: having meaning as a directory
- Easy fix remove bit about _ in class names
People want to create sub-packages without changing the namespace of code
- could be fixed mainly by ignoring subpackages they aren't a concept expressed in top-level naming only an installer feature, you would have to svn track a package and its subs which seems reasonable
People really like categories
- I'm pretty ambivalent, they could be made to work with svn but whats the point so much pear code doesn't really fix in one category
People want to be able to use aliased namespaces "use pear2::blah" "blah::Class"
- I see the want but you can do that within a package, really only makes sense with categories, special import function using class_alias is way nicer anyway for top level stuff
People want UC in their namespaces
- I'm not willing to budge on this, namespaces look like classes otherwise and it quickly gets confusing
People really really like pear1 ways
- They can keep using pear1 its not going away, i doubt any of them will upgrade to 5.3 this decade, we need to appeal to devs though no deal breakers in coding standards