Re: PEAR Coding Standards

ok this is now clear to me... was reading too fast and missed the important part :) > > 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 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------