Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:8699
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Reply-To: john@coggeshall.org
To: Georg Richter <georg@php.net>
Cc: George Schlossnagle <george@omniti.com>, Edin Kadribasic <edink@emini.dk>,  Marcus Boerger <helly@php.net>, PHP Internals <internals@lists.php.net>
In-Reply-To: <200403231858.57603.georg@php.net>
References: <1079935882.5524.0.camel@coogle.localdomain>
	 <6BE1F003-7CD2-11D8-875C-000393B2B3C0@omniti.com>
	 <1080050940.14199.11.camel@coogle.localdomain>
	 <200403231858.57603.georg@php.net>
Content-Type: text/plain
Message-ID: <1080072351.14294.6.camel@coogle.localdomain>
Mime-Version: 1.0
Date: Tue, 23 Mar 2004 15:05:51 -0500
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Studlycaps and MySQLi
From: john@coggeshall.org (John Coggeshall)

On Tue, 2004-03-23 at 12:58, Georg Richter wrote:
> Sure, your book isn't ready yet. Would be interesting to know your opinion if 
> it would be printed already. 

Then I really wouldn't care. In either case, this entire thread is
getting completely pointless. I don't care if studlyCaps or
underscore_methods are used or not, I'd just like to see it be one or
the other. Since everyone seems to have a major problem changing SQLite
and MySQLi, perhaps for good reason -- what about just changing ext/tidy
back to underscore_methods? At least then we'd be consistent, and
probably wouldn't have as much of a negative impact as changing the
database extensions would.

John

-- 
-=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=-
John Coggeshall                   http://www.coggeshall.org/
The PHP Developer's Handbook    http://www.php-handbook.com/
-=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=-