Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:1776 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 51723 invoked from network); 20 May 2003 11:14:23 -0000 Received: from unknown (HELO mail.dybnet.de) (195.75.116.243) by pb1.pair.com with SMTP; 20 May 2003 11:14:23 -0000 Received: (qmail 21491 invoked by uid 508); 20 May 2003 11:18:13 -0000 Received: from unknown (HELO vandal) (vandal@217.231.121.39) by www.dybnet.de with RC4-MD5 encrypted SMTP; 20 May 2003 11:18:13 -0000 To: Date: Tue, 20 May 2003 13:14:29 +0200 Organization: BackendMedia GbR Message-ID: <007401c31ec0$fc8d0400$4d00a8c0@vandal> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 In-Reply-To: <006d01c31ebf$926ed630$4d00a8c0@vandal> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Subject: RE: [PHP-DEV] RFC: PHP OO API naming convention From: smith@backendmedia.com ("Lukas Smith") References: <006d01c31ebf$926ed630$4d00a8c0@vandal> > From: Lukas Smith [mailto:smith@backendmedia.com] > Sent: Tuesday, May 20, 2003 1:04 PM > This is a follow up of a previous thread but this time I will give it > the RFC label to make it more official: > http://marc.theaimsgroup.com/?l=php-dev&m=105299997308470&w=2 > > I am proposing the use of studlyCaps as the CS standard for object > oriented API's exposed by PHP extensions. I was just informed that I am making this more complex than they need to be and that the first thread was enough. I will make the necessary modifications to the CODING_STANDARDS and will get someone to commit this. Regards, Lukas