Re: PEAR Coding Standards

oh, the standard is just saying to use the categorie name as constant prefix? so NET_TYPE_MESSAGE would be ok? > > See the naming standart: > http://pear.php.net/manual/en/standards.naming.php > > 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------