Re: [PEPr] Comment on RFC::Prefix all packages with P_

Hoi Ian, On 7/12/06, Ian Eure <ieure@blarg.net> wrote:

Prefixing everything and managing the dependency spaghetti afterwards is a massive effort, requiring coordination of / all/ PEAR devs, and a huge burden on QA when they pick up the slack for devs who are MIA.

I think we should add the requirement, that a package which is performing the prefix change may not go stable until all its dependencies have implemented the prefix change. I also think that the big packages have enough man power to rename their classes and update factories and singeltons. Small packages without maintainers may easily be updated by everyone. Just sent patches. As its a simple renaming auditing the patches can be done fast by QA.

Also, nobody has mentioned how this breaks existing package naming; for every existing package, we'd need a new package with the prefix, e.g. Foo -> P_Foo.

I added this as note to the RFC. This could be useful in a way that all new pear packages have the same base class. In this way we could force all packages to implement certain methods und a user could determine via instanceof if the object in question is a pear package in general. -- mit freundlichen Grüßen email ~ m@tacker.org Markus Tacker url ~ http://m.tacker.org/ icq ~ 91709561