> > Following a standard seems logical, following the PEAR coding standard > > sounds good to me. It's in the manual, makes sense, and is known to many. > > It is actually not in the manual anymore. PEAR has its own manual > now. The PEAR stuff in the main manual is not generated for output. > It is going to be removed.
Oh well, two of three isn't bad :) Expanding/modifying pears standard seems reasonable for phpdoc conventions. a) Should every example immediatly be modified to adhere to this? - Eventually, no rush. No single file commits please ;) b) Will people be shot for not following the standard? - Yes! You DID read the HOWTO right? :) +1 for having a coding standard for phpdoc examples. +1 for Goba writing an RFC this weekend :) Regards, Philip Olson
