Re: coding standard - not again!

On Thu, 20 Dec 2001 13:57:34 +0800, Alan Knowles wrote: >So at present we have a disparate mess (perhaps a bit strong) of code >residing all over the place, sourceforge, manual's site, (not to mention >half a dozen extra great sites.) > >Is there a way to address - well kind off - this is still half baked, >but may fly.... >prePEAR (or prepare), a less strict repostitory that is set up on the >assumtion that the packages will eventually be converted to PEAR >standards, either by the author or another volunteer. Some time ago we decided to split PEAR into a core and an 'extended' part. Code in the core has to correspond to the coding standards in every case. But we can perhaps define the coding standards for the extended part less strict: * The function naming scheme has to consistent all over the place -> don't change it. * Tabs vs. Spaces: We could allow tabs and spaces in the extended part. * Braces: Allow both styles: function foo() { } function bar() { } * ... Warning: This is no definitive plan, but perhaps it inspires some of us to think about this. - Martin -- Martin Jansen, <mail@martin-jansen.de> http://www.martin-jansen.de/