Re: PEAR Coding Standards

On Fri, 13 Dec 2002 22:53:13 +0100 Mirco "MEEBEY" Bauer <pear-dev@meebey.net> wrote: > > oh, the standard is just saying to use the categorie name as constant > prefix? so NET_TYPE_MESSAGE would be ok? SMARTIRC_TYPE_MESSAGE paste from doc (****==to read carefully): Constants Constants should always be all-uppercase, with underscores to separate words. Prefix constant names with the uppercased name of the ****class/package*** they are used in. For example, the constants used by the DB:: package all begin with "DB_". Global Variables If your package needs to define global variables, their name should start with a single underscore followed by the ****package name**** and another underscore. For example, the PEAR package uses a global variable called$_PEAR_destructor_object_list. As another advice, the last for today, trying to reduce name length for a lazy reason is really not a good idea... pierre