Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:6163
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <5.1.0.14.2.20031204004321.0a4cb8a8@127.0.0.1>
Date: Thu, 04 Dec 2003 00:45:02 +0200
To: ilia@prohost.org,internals@lists.php.net
In-Reply-To: <200312031750.34517.ilia@prohost.org>
References: <5.1.0.14.2.20031203223915.02f7fb00@127.0.0.1>
 <5.1.0.14.2.20031203223915.02f7fb00@127.0.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [PHP-DEV] StudlyCaps
From: andi@zend.com (Andi Gutmans)

I think you misunderstood what I said. I said that I support underscore 
naming, but it should be allowed in extensions which follow a specific 
standard such as DOM (W3C), obviously Java connectivity (that's really not 
under our control anyway because it depends on how you write your Java code).
Most extensions, such as mysqli, don't fall in this category and should 
thus use underscores.

Hope I made myself clearer now.

Andi

At 05:50 PM 12/3/2003 -0500, Ilia Alshanetsky wrote:
>-1
>
>*Caps syntax is harder to read & use compared to the underscore based system,
>which we already use. Having 2 separate naming conventions is confusing and
>difficult and you end up with the code which will mix & match both of them
>resulting in confusing and difficult to read code.
>
>Ilia
>
>--
>PHP Internals - PHP Runtime Development Mailing List
>To unsubscribe, visit: http://www.php.net/unsub.php