Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:6253
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Sat, 6 Dec 2003 17:14:04 +0100
To: internals@lists.php.net
Message-ID: <20031206161404.GA13130@prp0.prp.physik.tu-darmstadt.de>
References: <5.1.0.14.2.20031203223915.02f7fb00@127.0.0.1> <200312061001.hB6A1E8M032486@mailserver3.hrz.tu-darmstadt.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200312061001.hB6A1E8M032486@mailserver3.hrz.tu-darmstadt.de>
User-Agent: Mutt/1.3.27i
Subject: Re: [PHP-DEV] StudlyCaps
From: et@php.net (Stefan Walk)

On Sat, Dec 06, 2003 at 10:59:33AM +0100, Sebastian Bergmann wrote:
>   PHP's internal *function names* should use _ to delimit between
>   words.
[snip]
>   And this what we should *consistently* adopt for the naming of PHP's
>   internal *method names*.

Why should methods differ from functions in naming? That in itself is
inconsistency...

I'm in favour of naming with underscores, simply because that was the
PHP way until now and it helps readability a lot.

But i guess the only solution that both parties will accept is
dynamically removing all underscores from names when calling a
function/method (that would clear up the strpos/str_replace etc
inconsistency as well).

-- 
Regards,
Stefan Walk
<swalk@prp.physik.tu-darmstadt.de>