Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:6155
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <3FCE6317.5020405@leetspeak.org>
Date: Wed, 03 Dec 2003 23:26:31 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20030924 Thunderbird/0.3
MIME-Version: 1.0
To:  internals@lists.php.net
References: <5.1.0.14.2.20031203223915.02f7fb00@127.0.0.1> <62044F50-25D3-11D8-A17A-000393B2B3C0@omniti.com> <3FCE6046.8070509@leetspeak.org> <2745E411-25DF-11D8-A17A-000393B2B3C0@omniti.com>
In-Reply-To: <2745E411-25DF-11D8-A17A-000393B2B3C0@omniti.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] StudlyCaps
From: cm@leetspeak.org (Michael Walter)

George Schlossnagle wrote:
>> On the other hand, there are Common Lisp (foo-bar-baz), Python (mostly 
>> foobarbaz) and Ruby (mostly foo_bar_baz).
> 
> 
> To be pedantic, the Python style guide 
> (http://www.python.org/peps/pep-0008.html) specifies class names to be 
> StudlyCaps and method names to be either underscore-delimited or 
> StudlyCaps, at the authors leisure.  Of course, PHP is not Python.
The latter being my real point :) I don't really have an opinion on the 
subject (I'm fine with either style, as long as it's *consistent*), but 
I felt like pointing out that there isn't really one standard convention 
(as people might get the impression) even if you just consider languages 
supporting OO.

Cheers,
Michael