Re: CS questions
| From: | Klaus Guenther | Date: | Mon, 24 Nov 2003 12:14:12 +0000 |
| Subject: | Re: CS questions | ||
| References: | 1 2 3 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-233@lists.php.net to get a copy of this message | ||
Forgot to cc the list
From: "Arnaud Limbourg" <arnaud.limbourg@club-internet.fr>
Sent: Sunday, November 23, 2003 9:30 PM
> > > I think half of PEAR does it one way and half the other :-/
> >
> > Well, I'm for forcing studlyCaps for all properties (whether public or
not).
> > However, within the functions, I think we can leave it up to the
individual
> > developer (of course, arguments should be studlyCaps as well).
>
> I agree, inside functions we can leave that up. It doe not matter for
arguments
> because they are just used inside the methods.
Yes, but... they also appear in documentation (esp. api docs). I agree that
they can be left up to the developers.
> Class properties should use stuldy caps. But forcing the developers might
not be a good idea.
I don't think that should be a problem... after all, we use one true brace
for functions, and not everyone likes that, either. Not to mention the
existing naming scheme. It's a matter of uniformity.
Klaus