Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:3171 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 11105 invoked from network); 2 Jul 2003 17:21:03 -0000 Received: from unknown (HELO mail.zend.com) (192.117.235.230) by pb1.pair.com with SMTP; 2 Jul 2003 17:21:03 -0000 Received: (qmail 15476 invoked from network); 2 Jul 2003 17:20:59 -0000 Received: from localhost (HELO andi-home.zend.com) (127.0.0.1) by localhost with SMTP; 2 Jul 2003 17:20:59 -0000 Message-ID: <5.1.0.14.2.20030702202433.045aba78@127.0.0.1> X-Sender: andi@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 02 Jul 2003 20:24:55 +0200 To: "l0t3k" ,internals@lists.php.net In-Reply-To: <20030702143734.11223.qmail@pb1.pair.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: [PHP-DEV] PHP5 - OO extensions and naming conventions. From: andi@zend.com (Andi Gutmans) References: <20030702143734.11223.qmail@pb1.pair.com> At 10:37 AM 2/7/2003 -0400, l0t3k wrote: >IIRC there was an informal consensus to use studlyCaps as the official >userland convention for OOP extensions (*) (leaving aside the case >insensitivity of the language.) >my question now concerns accessors. should we prefer properties over >propertyGet()/propertySet() accessor functions ? would having both >constitute bloat. i ask because im implementing a series of classes >mirroring those in the Caffeinated Language (tm) so familiarity could be an >asset. > > >l0t3k >(*) i wonder if this should be more formalized before the next major >release. major extensions like dom/xsl are already using the current >method->function_ name() convention. I definitely prefer setXXX()/getXXX() functions over property overloading. Andi