Re: hope to finish the coding standard

It is so easy. Just allow tabs and spaces (1 tab == 4 spaces) AND the mentioned method naming and for a last specify the brace-rules and ony a real minority will complain in the future. Just make sure the proper settings for editors are kept within the files ... :) - Markus On Mon, Dec 24, 2001 at 08:35:53AM +0100, Stig S. Bakken wrote : > Alexander, > > I think you are romanticising and blowing this out of proportion. It > makes me uncomfortable that you compare PEAR's coding standards with the > bible, because that kinda confirms the image some people have of "us": > fanatics. > > I think the coding standards can be relaxed a bit. Their goal is to > create a common set of rules. But this community has to listen to its > (potential and regular) contributors. There are two issues that receive > most of the complaints: > > 1. method naming > > 2. tabs and spaces > > I think it's time to extend (1) to allow both studlyCaps and > under_scores. IMHO the strict studlyCaps rule has proven to be > sub-optimal for this community. If PEAR was a Java repository it would > probably be different, but it's a PHP community, and PHP's standard that > people are used to is using under_scores. > > When it comes to (2) I don't have any strong feelings about opening it > up, but there should be a reasonable "gripe limit". If lots and lots of > people complain, we cannot simply ignore them forever. That's just > arrogant. > > IMO we should relax the coding standards, once, and then have people > laminate it in plastic and put it on their wall. :-) There will be a > new round of changes preparing for ZE2, once the exact syntax and > semantics for exceptions are nailed down. > > Merry x-mas. > > - Stig > > Alexander Merz wrote: > > > > It's late at night, hm, more early in the morning, so don't wonder... > > > > I'm working as a voluntary for a non-profit association, which organizes > > concerts and parties with newcomer bands. Every Spring since two years, we > > organize a festival over three days. During this days we had 80 voluntarily > > aids. Every of them had to subscribe a sheet of paper with strict rules ( no > > drugs and alcohol, to be punctually etc.). Some break this rules and we "fired" > > them. > > > > Why we do this? Yes they are spending time for your stuff and we fire them, are > > we ungratefully? > > Maybe yes! But this is necessarily. To organize this festival is not your > > profession, but we run in a lot of trouble, if we are not doing all > > professional. And to do anything professional, you need rules. Some of the your > > aids didn't like this rules (me too, i was resonsible for the beer bar). But we > > all know, breaking them, would lead in a big failure. Although we had worked > > three hard days, everybody would laught about us and get bad publicity. > > > > Ok, what has this to do PEAR? A lot :-) > > > > We all are voluntaries, we are working for PEAR without get payed. As a > > 'virtual community' we need rules too, we call this rules Coding Standard. > > Somebody, uninteressted who created this rules, i really believe he created > > this standards, because he used this standards already. And? Everybody has it > > own style, thats a fact, but in a bigger organisation like PEAR you need one > > unique. A unique standard has a big advantage for quality keeping and required > > for working together. > > Every company has it coding standard, do you ignore them, when you entering the > > company? No! Having a coding standard is a big sign of professionality. Yes, > > you are a voluntary, and when we request professional work, we should be able > > to pay for this. But, we can't pay, we earn no money for PEAR :-) But please > > think one minute, what are you in your company and what are you as a PEAR > > developer? Working in your company, means nobody outside of the company, see > > what you are doing. You could be a genius, but would nobody knows it. PEAR is > > already used all over the world, the name of the programmer stands in the > > programm files, is mentioned on the website, in the PEAR manual, if you are a > > genius everbody would know it. But only, when you write the PEAR stuff in a > > good quality or just 'professional'. :-) > > > > Ok, you said we can change the standard. Yes we can really do it, but when we > > do it once, we can do it again, and again. Uninteresting which standard you > > have, there is at least one, who wants a other rule changed. > > > > The existing rules are 2 years old, they didn't changed, the bible is more then > > 2000 years old and still unchanged. And the result? The christian church is not > > the biggest religion, but still one of the worlds religion. If somebody didn't > > want to follow the coding standards and didn't want to join PEAR, it is OK! You > > can go to another OpenSource project, PEAR is not the only PHP code library. > > PEAR has special rules, since 2 years more then 20 developer can live with this > > rules and produces a lot of stable and useful code. > > > > Cu, Alex > > > > -- > > PEAR Development Mailing List (http://pear.php.net/) > > To unsubscribe, e-mail: pear-dev-unsubscribe@lists.php.net > > For additional commands, e-mail: pear-dev-help@lists.php.net > > To contact the list administrators, e-mail: php-list-admin@lists.php.net > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, e-mail: pear-dev-unsubscribe@lists.php.net > For additional commands, e-mail: pear-dev-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net -- Please always Cc to me when replying to me on the lists.