Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:6290
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <5.1.0.14.2.20031208214522.02a05fa0@127.0.0.1>
Date: Mon, 08 Dec 2003 21:49:07 +0200
To: internals@lists.php.net
In-Reply-To: <20031208121348.71285.qmail@web20416.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: End to StudlyCaps thread (hopefully)
From: andi@zend.com (Andi Gutmans)
References: <20031208121348.71285.qmail@web20416.mail.yahoo.com>

Hi guys,

I'd like to put an end to this thread.
Taking into account everyone's opinion I think the best solution is to go 
for StudlyCaps with OOP code.
Main reasons:
a) PEAR.
b) Interface with other OO models.
c) Status quo today with iterator and array access interfaces.

I don't think it's such a big deal, and although I slightly preferred 
underscores, I think it's the best to leave this issue go and finalize on 
StudlyCaps. As internals@ was pretty much split on this (probably with a 
slight advantage to StudlyCaps) I think it's the right way to go or we'll 
never get any closure. Having this rule will give us consistency across 
PEAR and PHP.

On another subject, Beta 3 is extremely close. I am just waiting for a few 
engine bugs to be nuked so please commit your final patches.

Thanks,
Andi