Standards ...

I'm obviously in a minority, but having checked back through ALL of my projects 
for the last ten+ years since starting to use PHP over C++ I can honestly say 
that I was not aware that PEAR did NOT follow what I took as the standard for 
PHP as described in the PHP coding_standards. All of my copies of the PEAR 
packages that I use ... imported from other project implementations ... use 
tabbed format files. My main library ADOdb is tabbed, and all of the projects I 
have worked on follow the same format. So the question I need answering is "WHY 
is the standard for PEAR actually different to the PHP coding_standards?"

All right the standards document does say "Of course, we can't and don't want to 
force anybody to use a style he or she is not used to" which is meant to be 
applied to private work? But at that time I was already used to tabbed format 
files. Also the suggestion is that the document was never meant to apply to 
'user land code', but in the absence of any alternative standard why would you 
NOT follow the core rules? As I have said already, why should there be one style 
for one set of files and another for in many cases the same files in a different 
usage?

Moving forward, the suggestion is that other projects are now following that 
standard because PEAR dictates it, and the current proposals are to standardise 
on that because "That is what everybody uses nowadays". By default therefore we 
have to start managing different coding standards depending on what we are 
working on at the time? Rather than sticking with the one previously established 
standard?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk