Date: Tue, 20 Jan 2004 23:13:06 +0100
To: andi@php.net
Subject: CSHi,
there still seems to be confusion about the CS for OO code and since
Derick reverted the studlyCaps guidelines there is nothing in the CS style.Could you revert the last commit back to version 1.26?
Guys,
I remember we agreed that OO code will have studlyCaps. I don't want to
have this long thread again (I was actually initially opposed but got
convinced/gave in).
As I don't have the time right now nor the setup, can someone please revert
and put the studlyCaps guidelines for OO extensions back into the Code
Guidelines?
Andi
I remember we agreed that OO code will have studlyCaps. I don't want to
have this long thread again (I was actually initially opposed but got
convinced/gave in).
You don't want a long thread? Then don't mention the topic.
As I don't have the time right now nor the setup, can someone please revert
and put the studlyCaps guidelines for OO extensions back into the Code
Guidelines?
Nay. Derick was right about removing that section.
- Sascha
Hello Sascha,
Wednesday, January 21, 2004, 8:21:30 AM, you wrote:
I remember we agreed that OO code will have studlyCaps. I don't want to
have this long thread again (I was actually initially opposed but got
convinced/gave in).
You don't want a long thread? Then don't mention the topic.
As I don't have the time right now nor the setup, can someone please revert
and put the studlyCaps guidelines for OO extensions back into the Code
Guidelines?
Nay. Derick was right about removing that section.
Yesturday we had an irc discussion about this issue too. And we came to the
conclusion once again that all oo guys wnat it and only a few non oo guys
don't want it. Besides such things it was meant to make php objects
consistent intheir naming scheme and consisten with the rest of the oo world
too. The main point against it was that we couldn't keep the original
writing in error messages, reflection and such. Now we can and all oo
extensions follow studlyCaps i put it back. Thanks Andi for noticing it
once again.
--
Best regards,
Marcus mailto:helly@php.net
At 08:21 AM 1/21/2004 +0100, Sascha Schumann wrote:
I remember we agreed that OO code will have studlyCaps. I don't want to
have this long thread again (I was actually initially opposed but got
convinced/gave in).You don't want a long thread? Then don't mention the topic.
I don't want another long thread because we came to agreement on the
previous one. If you don't like the result that's your problem.
As I don't have the time right now nor the setup, can someone please revert
and put the studlyCaps guidelines for OO extensions back into the Code
Guidelines?Nay. Derick was right about removing that section.
see above. Derick did this without consultation and even if you agree or
don't agree with it, he shouldn't have done it in the first place.
Andi
At 08:21 AM 1/21/2004 +0100, Sascha Schumann wrote:
I remember we agreed that OO code will have studlyCaps. I don't want to
have this long thread again (I was actually initially opposed but got
convinced/gave in).You don't want a long thread? Then don't mention the topic.I don't want another long thread because we came to agreement on the
previous one. If you don't like the result that's your problem.
Huh? There certainly was no agreement. The thread basically
closed with you declaring that you changed your opinion. But
you are not the judge (nor am I). No agreement in sight.
- Sascha
see above. Derick did this without consultation and even if you agree or
don't agree with it, he shouldn't have done it in the first place.
I added it without consultation too, that was wrong, so I corrected it :)
Derick