Re: CS questions
| From: | Arnaud Limbourg | Date: | Sun, 23 Nov 2003 20:30:15 +0000 |
| Subject: | Re: CS questions | ||
| References: | 1 2 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-230@lists.php.net to get a copy of this message | ||
> > Which would also mean that LiveUser would have to fix it's class names and
> > prepend them with a 'Perm_'.
>
> Fortunately, LiveUser hasn't reached 1.0 yet :-) And the package name should
> be changed to Perm_LiveUser. Of course, now is the time to hash out the
> exact category.
The problem of liveuser is that it falls under both auth and perm since it is a framework. So i
don't really think it would be a good idea to rename it (defending the ground ;)
> > 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.
Class properties should use stuldy caps. But forcing the developers might not be a good idea.
Arnaud.