RE: [PEAR-DEV] hope to finish the coding standard

Hello, Merry Christmas ... Anyways onto the issue at hand :-) > > 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 > I already wrote in a lot of mails that the coding standard is handled > relaxed > in practice. Uhm one of the first things I saw when I joined the list was someone getting slammed for not having followed the naming convention while his components were in the early stages of being adopted. > So far I remember there are only two, which said, we are not willing to > contribute our classes due to the cs. I assume the rate of people that went to the PEAR site, started reading the docs and found out that the only thing that is documented is the CS (this is changing). But it is the thing that is waved in their faces first. And that was a major turn off then I first went to the PEAR site quite a while back and I only joined the dev list because of the DB abstraction project. > Which community? Allow both style it is optimal for devs, but really > non-optimal for the user. Actually for me naming conventions are not a big deal. I would mind changing my code across my entire application framework to fit PEAR's naming conventions. But for new code I don't have a problem to use the PEAR naming conventions. I do have a problem having to reconfigure my editor to fit PEAR, or worse having to go back and forth. In the end I benefit from a smooth working experience with the 4 other PHP developers in my company more than from PEAR. > At least it is a question of discipline. If you are not willing to adopt > your > code to cs, why should you willing to maintain and to document your class? Huh? Of course following a CS is a matter of discipline but why do you think PEAR's CS is the only one that exist? And for all intents and purposes PEAR's CS always looses against company CS's. And not having the time or nerve to change code that works perfectly well for them every freaking time they make changes (because yes they might have to follow a CS at their company, so they will have to maintain the same code in 2 different formats; btw Wrappers are a nice way to solve backwards compatibility issues but not to solve cooperation between incompatible CS's) it's just not worth it. This has nothing to do with showing that you will maintain your code. Best regards, Lukas Smith smith@dybnet.de _______________________________ DybNet Internet Solutions GbR Alt Moabit 89 10559 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de info@dybnet.de _______________________________