# StudlyCaps

- Thread: https://externals.io/message/6252
- Original archive: https://news-web.php.net/php.internals/6252
- Started by Marc Dembogurski on 2003-12-06T15:16:54+00:00
- Messages: 1
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #6252 — Marc Dembogurski — 2003-12-06T15:16:54+00:00

URL: https://externals.io/message/6252#6252

Sebastian Bergmann wrote:
>Andi Gutmans wrote:
> > […]
>
>  PHP's internal *function names* should use _ to
delimit between
>  words.
>
> > […]
StudlyCaps.
>
>  And this what we should *consistently* adopt for
the naming of PHP's
>  internal *method names*.
>  So, of course, I am +1 for studlyCaps. But
regardless of a pro/con
>  decision on studlyCaps the result must be
consistent.

Sebastian is RIGHT, but shall consider that not
adopting studlyCaps  probably will cause inconsistency
since some existent object models WONT change.

So, as other people said, its not a matter of personal
tastes. 

Defining underscores as STANDARD to OO related code
will just create the inconsistency Sebastian told.

And the consequenses will be seen in the future, when
PHP will have both code using underscores and
studlyCaps for OO related code.

Someone has doubts it will happen?????????

__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/