Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:1529 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22910 invoked from network); 15 May 2003 13:21:12 -0000 Received: from unknown (HELO jdi.jdimedia.nl) (212.204.192.51) by pb1.pair.com with SMTP; 15 May 2003 13:21:12 -0000 Received: from jdi.jdimedia.nl (jdi.jdimedia.nl [212.204.192.51]) by jdi.jdimedia.nl (8.12.4/8.12.4) with ESMTP id h4FDL87A012232; Thu, 15 May 2003 15:21:08 +0200 Date: Thu, 15 May 2003 15:21:08 +0200 (CEST) X-X-Sender: derick@jdi.jdimedia.nl To: Sterling Hughes cc: Lukas Smith , internals@lists.php.net In-Reply-To: <1052999404.27984.127.camel@hasele> Message-ID: References: <001501c31ad9$76f503a0$4d00a8c0@vandal> <1052999404.27984.127.camel@hasele> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] PHP OO naming conventions From: derick@php.net (Derick Rethans) On Thu, 15 May 2003, Sterling Hughes wrote: > I agree with lukas - I think our methods should follow studlyCap naming > conventions. same here, not because I like them, but because it's a standard. (I would hate to see this happen for normal functions though). Derick -- "my other box is your windows PC" ------------------------------------------------------------------------- Derick Rethans http://derickrethans.nl/ PHP Magazine - PHP Magazine for Professionals http://php-mag.net/ -------------------------------------------------------------------------