Re: PEAR Coding Standards

I don't want to start a troll, but I just wanted to point to this problem... done. I accept the standards of course. About that namespace thing, ZE2 (Zend Engine2) allows to use different namespace for each class, so my TYPE_QUERY wouldn't conflict with other classes using TYPE_QUERY :) this feature is really neat.. but ZE2 is still kinda future/under development/nice to have thing... > > I see it. And that sounds quit logical to me. For instance check > XML_XSLT_Wrapper if you want see longer constants names. This is > definitivly not a problem. Good&readable code is usually not equal to > short name. > > And you catch a point with TYPE_QUERY, this name may exist is too many > packages as you can imagine :) > > Namespaced constants, how can you manage it ? even with a real namespace > ? > > To avoid a troll, this is the *standart*, just apply it even you do not > like it :-) > > hth > > pierre Mirco Bauer aka MEEBEY -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d s-: a--- C++ UL++>++++ P L++$>+++$ E W+++$ N o? K- w++>! O- M- V? PS PE+ Y- PGP>++ t 5+ X++ R tv+ b+ DI? D+ G>++ e h! r>++ y? ------END GEEK CODE BLOCK------