Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:6285 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 31104 invoked by uid 1010); 8 Dec 2003 12:13:50 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 31078 invoked from network); 8 Dec 2003 12:13:49 -0000 Received: from unknown (HELO web20416.mail.yahoo.com) (66.163.169.92) by pb1.pair.com with SMTP; 8 Dec 2003 12:13:49 -0000 Message-ID: <20031208121348.71285.qmail@web20416.mail.yahoo.com> Received: from [200.203.29.166] by web20404.mail.yahoo.com via HTTP; Mon, 08 Dec 2003 04:13:48 PST Date: Mon, 8 Dec 2003 04:13:48 -0800 (PST) To: internals@lists.php.net MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [PHP-DEV] StudlyCaps From: marc_dembogurski@yahoo.com (Marc Dembogurski) Cristiano Duarte wrote: >IMHO we shouldn't have exceptions. If the DOM extension (and many others) >must use StudlyCaps (because of W3C specifications), all OO-based extension or >code should use too. >We can live with a CS for procedural and other CS for OOP. >Cristiano Duarte Yes, Look at what Cristiano and other people saying: "IMHO we shouldn't have EXCEPTIONS".... Exceptions are consistent ???? I have the answer: NO!!!! As I said before, I prefer to use underscores, but in this case, with PEAR Using caps and other extensions will use caps, so why turn it into a mess?????? I know I am not a core developer, but as an OLD analyst I can say that underscores for OO are the wrong choice now. Using caps for OO code and underscores for procedural will make things easier in the future.... Think about it. Regards __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/