# [PHP-CVS] cvs: php-src / CODING_STANDARDS

- Thread: https://externals.io/message/6108
- Original archive: https://news-web.php.net/php.internals/6108
- Started by Sascha Schumann on 2003-12-03T15:52:43+00:00
- Messages: 2
- 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

---

## #6108 — Sascha Schumann — 2003-12-03T15:52:43+00:00

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

> > […]
>
> > […]
>
> Well if I extend a class that doesnt use studlyCaps, yet the PEAR CS
> requires that I use studlyCaps, then I have a problem. Essentially I can
> only wrap and not extend. I guess you can say this is our problem however,
> since we could also choose to loosen our CS to allow underscores.

    Agreed.

> I don't
> feel that having to ways in there is the way to go. I prefer to stay with
> one which results in the fewest breaks with the outside world.

    You apparently live in an alternative "outside world".  In
    mine, there are 99% C bindings where studlyCaps virtually do
    not exist.

    - Sascha

---

## #6111 — Lukas Smith — 2003-12-03T16:00:15+00:00

URL: https://externals.io/message/6108#6111 · In reply to: #6108

> From: Sascha Schumann [mailto:sascha@schumann.cx]
> Sent: Wednesday, December 03, 2003 4:53 PM
> 
> 
> 
> > […]
> objects
> > […]
> however,
> > […]
> 
>     Agreed.
> 
> > […]
> with
> > […]
> 
>     You apparently live in an alternative "outside world".  In
>     mine, there are 99% C bindings where studlyCaps virtually do
>     not exist.

And here is the other difference in opinion:
To me procedural APIs bound to an OO API "break" their heritage and so I
don't have a problem of going to studlyCaps. Actually I think it is even an
advantage because it makes me differentiate procedural code from OO code
more easily. But now we are getting into aesthetics again :-)

So it goes .. I don't feel I have anything to add beyond what I have said so
far and I hope I haven't wasted peoples time (even if the only value was to
reassure the opinion that studlyCaps is not for PHP).

Regards,
Lukas