Re: PEAR Coding Standards

The request was givin with the reason of a new PEAR package called Net_SmartIRC... About the constants, the developer that use my class then has for instance todo this: register_actionhandler(NET_SMARTIRC_TYPE_QUERY|NET_SMARTIRC_TYPE_NOTICE, '^test', $bot, 'query_test'); instead of: register_actionhandler(TYPE_QUERY|TYPE_NOTICE, '^test', $bot, 'query_test'); see the differenz? PHP needs own namespaces for classes (ZE2 has to come...) > > It s trivial to replace them all, that may not be ugly, maybe longer > names. But you have to think about people who use not only your class. > The naming standart will prevent names conflict for everything. > > Beside that, as a little advice, you may wait for your cvs account (and > drop a note in your account request about your pear package accepted on > peardev, so you will get your access to pear cvs and peardoc), then > pearify your code before any release. > > 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------