I don't think anyone means 'use pear' in the examples, just the standard. Like, what makes for a defining a function, construct spacing, etc. Odds are the pear coding standard will be a base which will be modified to suit phpdoc needs.
Regarding whether to use echo or print, concat variables or not, etc. No need to get that specific imho. Just the basics, like formatting. And fwiw, I'm against forcing 'or die' formatting in any example, it's not all that flexible. Regards, Philip Olson On Sun, 23 Dec 2001, James Moore wrote: > > > > > What do others think about that? > > I give a +1 for adapting the PEAR coding standard for Manual examples. > > -1 for anything complicated in the manual. Keep everything clear and concise > why do we need to clutter examples with PEAR error everywhere (Nothing > against pear I think its great but I dont think its all that clear for > examples in a manual.) Most code out there isnt written with PEAR at all and > thus when comparing code and the manual it might be unclear to the reader. > > - James >
