Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:6144
Return-Path: <helly@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 86977 invoked by uid 1010); 3 Dec 2003 21:51:48 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 86941 invoked from network); 3 Dec 2003 21:51:47 -0000
Received: from unknown (HELO shiva.mind.de) (212.42.230.204)
  by pb1.pair.com with SMTP; 3 Dec 2003 21:51:47 -0000
Received: from [192.168.1.100] (p508E9496.dip.t-dialin.net [80.142.148.150])
	by shiva.mind.de (Postfix) with ESMTP
	id 5E92E97C6D; Wed,  3 Dec 2003 22:51:41 +0100 (CET)
Date: Wed, 3 Dec 2003 22:51:51 +0100
Reply-To: Marcus Boerger <helly@php.net>
X-Priority: 3 (Normal)
Message-ID: <14693374390.20031203225151@marcus-boerger.de>
To: Andi Gutmans <andi@zend.com>
Cc: internals@lists.php.net
In-Reply-To: <5.1.0.14.2.20031203223915.02f7fb00@127.0.0.1>
References: <5.1.0.14.2.20031203223915.02f7fb00@127.0.0.1>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] StudlyCaps
From: helly@php.net (Marcus Boerger)

Hello Andi,

i am pro studlyCaps.
1st it eases PEAR development towards php5.
2nd we choose not to do so as we couldn't show errors and all in original
casing, now we can we decided to use studlyCaps and we agreed upon even in
our CODING_STYLE (and we did whether or not that rule was removed today).
3rd using different naming conventions in procedural and oo code seems to be
a pro from my point of view, too.

-- 
Best regards,
 Marcus                            mailto:helly@php.net