Re: Coding standards

On Fri, Dec 21, 2001 at 12:04:21AM +0100, Alexander Merz wrote: > > standards to would relax the majority of the style requirements. > > Which majority? Well, maybe not the majority numerically, but mainly: - Naming conventions (bumpy style) - Brace placement I think indenting should remain at four spaces (no tabs). I'm flexible here, too, however. > I see max. four people discussing this stuff. I keep hearing people tell me how our (my) style standards keep turning people off from PEAR. It's brought up often enough to warrant some kind of action. > The PEAR 'core'-developer ignore this thread, because they > found the discussion boring (according to talks on irc). I don't have the time to participate in IRC discussions. > > Next, we add a single (strict!) requirement that, when making > > changes to existing code in the repository, the changes must > > honor the style of the original file. Gross style-related > > Do you know the consequences of this? Of course I do. I wouldn't have suggested it otherwise. > This means, i have to analyze the file - tab, spaces, braces, > indention, naming. Then 30 min later, after changing the editor > settings, i can edit this file. This decreases the intrest in > quality control and bugfixing. Funny, I hear the same argument from the other team, too. Is it really such a bad thing that you be asked to understand the organization of a piece of code before you start working on it? Because I'd prefer to leave the spacing issue alone, you would only have to absorb the syntactic (not sure if that's the correct word) style of the original author. -- Jon Parise (jon@csh.rit.edu) . Information Technology (2001) http://www.csh.rit.edu/~jon/ : Computer Science House Member